Apparatus, system and method of communicating a wireless communication frame with a header

ABSTRACT

Some demonstrative embodiments include apparatuses, devices, systems and methods of communicating a wireless communication frame. For example, a wireless station may generate a frame including a header portion, the header portion including a legacy header, followed by a first non-legacy header, the header portion including a first indication to indicate whether or not the header portion is to include a second non-legacy header following the first non-legacy header, the header portion including a second indication to indicate whether or not channel bonding is to be used; and process transmission of the frame to at least one second wireless station over a directional wireless communication band.

CROSS REFERENCE

This application claims the benefit of and priority from U.S.Provisional Patent Application No. 62/154,910 entitled “Apparatus,System and Method of Wireless Communication using a Physical LayerHeader”, filed Apr. 30, 2015, the entire disclosure of which isincorporated herein by reference.

TECHNICAL FIELD

Embodiments described herein generally relate to communicating awireless communication frame with a header.

BACKGROUND

A wireless communication network in a millimeter-wave band may providehigh-speed data access for users of wireless communication devices.

According to some Specifications and/or Protocols, devices may beconfigured to perform all transmissions and receptions over a singlechannel bandwidth (BW).

Some Specifications may be configured to support a Single User (SU)system, in which a Station (STA) cannot transmit frames to more than asingle STA at a time.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements may be exaggerated relative to otherelements for clarity of presentation. Furthermore, reference numeralsmay be repeated among the figures to indicate corresponding or analogouselements. The figures are listed below.

FIG. 1 is a schematic block diagram illustration of a system, inaccordance with some demonstrative embodiments.

FIG. 2 is a schematic illustration of a Single Carrier (SC) PhysicalLayer (PHY) header.

FIG. 3 is a schematic illustration of a frame structure, in accordancewith some demonstrative embodiments.

FIG. 4 is a schematic illustration of a header structure, in accordancewith some demonstrative embodiments.

FIG. 5 is a schematic illustration of subfields of a non-legacy headerin a frame structure, in accordance with some demonstrative embodiments.

FIG. 6 is a schematic flow-chart illustration of a method ofcommunicating a wireless communication frame, in accordance with somedemonstrative embodiments.

FIG. 7 is a schematic illustration of a product of manufacture, inaccordance with some demonstrative embodiments.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of some embodiments.However, it will be understood by persons of ordinary skill in the artthat some embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components, unitsand/or circuits have not been described in detail so as not to obscurethe discussion.

Discussions herein utilizing terms such as, for example, “processing”,“computing”, “calculating”, “determining”, “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulate and/or transform datarepresented as physical (e.g., electronic) quantities within thecomputer's registers and/or memories into other data similarlyrepresented as physical quantities within the computer's registersand/or memories or other information storage medium that may storeinstructions to perform operations and/or processes.

The terms “plurality” and “a plurality”, as used herein, include, forexample, “multiple” or “two or more”. For example, “a plurality ofitems” includes two or more items.

References to “one embodiment”, “an embodiment”, “demonstrativeembodiment”, “various embodiments” etc., indicate that the embodiment(s)so described may include a particular feature, structure, orcharacteristic, but not every embodiment necessarily includes theparticular feature, structure, or characteristic. Further, repeated useof the phrase “in one embodiment” does not necessarily refer to the sameembodiment, although it may.

As used herein, unless otherwise specified the use of the ordinaladjectives “first”, “second”, “third” etc., to describe a common object,merely indicate that different instances of like objects are beingreferred to, and are not intended to imply that the objects so describedmust be in a given sequence, either temporally, spatially, in ranking,or in any other manner.

Some embodiments may be used in conjunction with various devices andsystems, for example, a User Equipment (UE), a Mobile Device (MD), awireless station (STA), a Personal Computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, an Internet of Things (IoT) device, a sensor device, a servercomputer, a handheld computer, a handheld device, a Personal DigitalAssistant (PDA) device, a handheld PDA device, an on-board device, anoff-board device, a hybrid device, a vehicular device, a non-vehiculardevice, a mobile or portable device, a consumer device, a non-mobile ornon-portable device, a wireless communication station, a wirelesscommunication device, a wireless Access Point (AP), a wired or wirelessrouter, a wired or wireless modem, a video device, an audio device, anaudio-video (A/V) device, a wired or wireless network, a wireless areanetwork, a Wireless Video Area Network (WVAN), a Local Area Network(LAN), a Wireless LAN (WLAN), a Personal Area Network (PAN), a WirelessPAN (WPAN), and the like.

Some embodiments may be used in conjunction with devices and/or networksoperating in accordance with existing Wireless-Gigabit-Alliance (WGA)specifications (Wireless Gigabit Alliance, Inc WiGig MAC and PHYSpecification Version 1.1, April 2011, Final specification) and/orfuture versions and/or derivatives thereof, devices and/or networksoperating in accordance with existing IEEE 802.11 standards (IEEE802.11-2012, IEEE Standard for Information technology—Telecommunicationsand information exchange between systems Local and metropolitan areanetworks—Specific requirements Part 11: Wireless LAN Medium AccessControl (MAC) and Physical Layer (PHY) Specifications, Mar. 29, 2012;IEEE802.11ac-2013 (“IEEE P802.11ac-2013, IEEE Standard for InformationTechnology—Telecommunications and Information Exchange BetweenSystems—Local and Metropolitan Area Networks—Specific Requirements—Part11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment 4: Enhancements for Very High Throughput forOperation in Bands below 6 GHz”, December, 2013); IEEE 802.11ad (“IEEEP802.11ad-2012, IEEE Standard for InformationTechnology—Telecommunications and Information Exchange BetweenSystems—Local and Metropolitan Area Networks—Specific Requirements—Part11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment 3: Enhancements for Very High Throughput in the60 GHz Band”, 28 Dec., 2012); IEEE-802.11REVmc (“IEEE802.11-REVmcm/D3.0, June 2014 draft standard for Informationtechnology—Telecommunications and information exchange between systemsLocal and metropolitan area networks Specific requirements; Part 11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specification”); IEEE802.11-ay (P802.11ay Standard for InformationTechnology—Telecommunications and Information Exchange Between SystemsLocal and Metropolitan Area Networks—Specific Requirements Part 11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment: Enhanced Throughput for Operation inLicense-Exempt Bands Above 45 GHz)) and/or future versions and/orderivatives thereof, devices and/or networks operating in accordancewith existing Wireless Fidelity (WiFi) Alliance (WFA) Peer-to-Peer (P2P)specifications (WiFi P2P technical specification, version 1.2, 2012)and/or future versions and/or derivatives thereof, devices and/ornetworks operating in accordance with existing cellular specificationsand/or protocols, e.g., 3rd Generation Partnership Project (3GPP), 3GPPLong Term Evolution (LTE) and/or future versions and/or derivativesthereof, units and/or devices which are part of the above networks, andthe like.

Some embodiments may be used in conjunction with one way and/or two-wayradio communication systems, cellular radio-telephone communicationsystems, a mobile phone, a cellular telephone, a wireless telephone, aPersonal Communication Systems (PCS) device, a PDA device whichincorporates a wireless communication device, a mobile or portableGlobal Positioning System (GPS) device, a device which incorporates aGPS receiver or transceiver or chip, a device which incorporates an RFIDelement or chip, a Multiple Input Multiple Output (MIMO) transceiver ordevice, a Single Input Multiple Output (SIMO) transceiver or device, aMultiple Input Single Output (MISO) transceiver or device, a devicehaving one or more internal antennas and/or external antennas, DigitalVideo Broadcast (DVB) devices or systems, multi-standard radio devicesor systems, a wired or wireless handheld device, e.g., a Smartphone, aWireless Application Protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems, for example, RadioFrequency (RF), Infra Red (IR), Frequency-Division Multiplexing (FDM),Orthogonal FDM (OFDM), Orthogonal Frequency-Division Multiple Access(OFDMA), FDM Time-Division Multiplexing (TDM), Time-Division MultipleAccess (TDMA), Multi-User MIMO (MU-MIMO), Spatial Division MultipleAccess (SDMA), Extended TDMA (E-TDMA), General Packet Radio Service(GPRS), extended GPRS, Code-Division Multiple Access (CDMA), WidebandCDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA,Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®,Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™, Ultra-Wideband(UWB), Global System for Mobile communication (GSM), 2G, 2.5G, 3G, 3.5G,4G, Fifth Generation (5G), or Sixth Generation (6G) mobile networks,3GPP, Long Term Evolution (LTE), LTE advanced, Enhanced Data rates forGSM Evolution (EDGE), or the like. Other embodiments may be used invarious other devices, systems and/or networks.

The term “wireless device”, as used herein, includes, for example, adevice capable of wireless communication, a communication device capableof wireless communication, a communication station capable of wirelesscommunication, a portable or non-portable device capable of wirelesscommunication, or the like. In some demonstrative embodiments, awireless device may be or may include a peripheral that is integratedwith a computer, or a peripheral that is attached to a computer. In somedemonstrative embodiments, the term “wireless device” may optionallyinclude a wireless service.

The term “communicating” as used herein with respect to a communicationsignal includes transmitting the communication signal and/or receivingthe communication signal. For example, a communication unit, which iscapable of communicating a communication signal, may include atransmitter to transmit the communication signal to at least one othercommunication unit, and/or a communication receiver to receive thecommunication signal from at least one other communication unit. Theverb communicating may be used to refer to the action of transmitting orthe action of receiving. In one example, the phrase “communicating asignal” may refer to the action of transmitting the signal by a firstdevice, and may not necessarily include the action of receiving thesignal by a second device. In another example, the phrase “communicatinga signal” may refer to the action of receiving the signal by a firstdevice, and may not necessarily include the action of transmitting thesignal by a second device.

Some demonstrative embodiments may be used in conjunction with a WLAN,e.g., a wireless fidelity (WiFi) network. Other embodiments may be usedin conjunction with any other suitable wireless communication network,for example, a wireless area network, a “piconet”, a WPAN, a WVAN andthe like.

Some demonstrative embodiments may be used in conjunction with awireless communication network communicating over a frequency band of 60GHz. However, other embodiments may be implemented utilizing any othersuitable wireless communication frequency bands, for example, anExtremely High Frequency (EHF) band (the millimeter wave (mmWave)frequency band), e.g., a frequency band within the frequency band ofbetween 20 Ghz and 300 GHZ, a frequency band above 45 GHZ, a frequencyband below 20 GHZ, e.g., a Sub 1 GHZ (S1G) band, a 2.4 GHz band, a 5 GHZband, a WLAN frequency band, a WPAN frequency band, a frequency bandaccording to the WGA specification, and the like.

The term “antenna”, as used herein, may include any suitableconfiguration, structure and/or arrangement of one or more antennaelements, components, units, assemblies and/or arrays. In someembodiments, the antenna may implement transmit and receivefunctionalities using separate transmit and receive antenna elements. Insome embodiments, the antenna may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements. The antenna may include, for example, a phased array antenna,a single element antenna, a set of switched beam antennas, and/or thelike.

The phrases “directional multi-gigabit (DMG)” and “directional band”(DBand), as used herein, may relate to a frequency band wherein theChannel starting frequency is above 45 GHz. In one example, DMGcommunications may involve one or more directional links to communicateat a rate of multiple gigabits per second, for example, at least 1Gigabit per second, e.g., 7 Gigabit per second, or any other rate.

Some demonstrative embodiments may be implemented by a DMG STA (alsoreferred to as a “mmWave STA (mSTA)”), which may include for example, aSTA having a radio transmitter, which is capable of operating on achannel that is within the DMG band. The DMG STA may perform otheradditional or alternative functionality. Other embodiments may beimplemented by any other apparatus, device and/or station.

Reference is made to FIG. 1, which schematically illustrates a system100, in accordance with some demonstrative embodiments.

As shown in FIG. 1, in some demonstrative embodiments, system 100 mayinclude one or more wireless communication devices. For example, system100 may include a first wireless communication device 102, a secondwireless communication device 140, and/or one more other devices.

In some demonstrative embodiments, devices 102 and/or 140 may include amobile device or a non-mobile, e.g., a static, device.

For example, devices 102 and/or 140 may include, for example, a UE, anMD, a STA, an AP, a PC, a desktop computer, a mobile computer, a laptopcomputer, an Ultrabook™ computer, a notebook computer, a tabletcomputer, a server computer, a handheld computer, a handheld device, anInternet of Things (IoT) device, a sensor device, a PDA device, ahandheld PDA device, an on-board device, an off-board device, a hybriddevice (e.g., combining cellular phone functionalities with PDA devicefunctionalities), a consumer device, a vehicular device, a non-vehiculardevice, a mobile or portable device, a non-mobile or non-portabledevice, a mobile phone, a cellular telephone, a PCS device, a PDA devicewhich incorporates a wireless communication device, a mobile or portableGPS device, a DVB device, a relatively small computing device, anon-desktop computer, a “Carry Small Live Large” (CSLL) device, an UltraMobile Device (UMD), an Ultra Mobile PC (UMPC), a Mobile Internet Device(MID), an “Origami” device or computing device, a device that supportsDynamically Composable Computing (DCC), a context-aware device, a videodevice, an audio device, an A/V device, a Set-Top-Box (STB), a Blu-raydisc (BD) player, a BD recorder, a Digital Video Disc (DVD) player, aHigh Definition (HD) DVD player, a DVD recorder, a HD DVD recorder, aPersonal Video Recorder (PVR), a broadcast HD receiver, a video source,an audio source, a video sink, an audio sink, a stereo tuner, abroadcast radio receiver, a flat panel display, a Personal Media Player(PMP), a digital video camera (DVC), a digital audio player, a speaker,an audio receiver, an audio amplifier, a gaming device, a data source, adata sink, a Digital Still camera (DSC), a media player, a Smartphone, atelevision, a music player, or the like.

In some demonstrative embodiments, device 102 may include, for example,one or more of a processor 191, an input unit 192, an output unit 193, amemory unit 194, and/or a storage unit 195; and/or device 140 mayinclude, for example, one or more of a processor 181, an input unit 182,an output unit 183, a memory unit 184, and/or a storage unit 185.Devices 102 and/or 140 may optionally include other suitable hardwarecomponents and/or software components. In some demonstrativeembodiments, some or all of the components of one or more of devices 102and/or 140 may be enclosed in a common housing or packaging, and may beinterconnected or operably associated using one or more wired orwireless links. In other embodiments, components of one or more ofdevices 102 and/or 140 may be distributed among multiple or separatedevices.

In some demonstrative embodiments, processor 191 and/or processor 181may include, for example, a Central Processing Unit (CPU), a DigitalSignal Processor (DSP), one or more processor cores, a single-coreprocessor, a dual-core processor, a multiple-core processor, amicroprocessor, a host processor, a controller, a plurality ofprocessors or controllers, a chip, a microchip, one or more circuits,circuitry, a logic unit, an Integrated Circuit (IC), anApplication-Specific IC (ASIC), or any other suitable multi-purpose orspecific processor or controller. Processor 191 executes instructions,for example, of an Operating System (OS) of device 102 and/or of one ormore suitable applications. Processor 181 executes instructions, forexample, of an Operating System (OS) of device 140 and/or of one or moresuitable applications.

In some demonstrative embodiments, input unit 192 and/or input unit 182may include, for example, a keyboard, a keypad, a mouse, a touch-screen,a touch-pad, a track-ball, a stylus, a microphone, or other suitablepointing device or input device. Output unit 193 and/or output unit 183may include, for example, a monitor, a screen, a touch-screen, a flatpanel display, a Light Emitting Diode (LED) display unit, a LiquidCrystal Display (LCD) display unit, a plasma display unit, one or moreaudio speakers or earphones, or other suitable output devices.

In some demonstrative embodiments, memory unit 194 and/or memory unit184 may include, for example, a Random Access Memory (RAM), a Read OnlyMemory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flashmemory, a volatile memory, a non-volatile memory, a cache memory, abuffer, a short term memory unit, a long term memory unit, or othersuitable memory units. Storage unit 195 and/or storage unit 185includes, for example, a hard disk drive, a floppy disk drive, a CompactDisk (CD) drive, a CD-ROM drive, a DVD drive, or other suitableremovable or non-removable storage units. Memory unit 194 and/or storageunit 195, for example, may store data processed by device 102. Memoryunit 184 and/or storage unit 185, for example, may store data processedby device 140.

In some demonstrative embodiments, wireless communication devices 102and/or 140 may be capable of communicating content, data, informationand/or signals via a wireless medium (WM) 103. In some demonstrativeembodiments, wireless medium 103 may include, for example, a radiochannel, a cellular channel, an RF channel, a Wireless Fidelity (WiFi)channel, an IR channel, a Bluetooth (BT) channel, a Global NavigationSatellite System (GNSS) Channel, and the like.

In some demonstrative embodiments, WM 103 may include a directionalchannel. For example, WM 103 may include a millimeter-wave (mmWave)wireless communication channel.

In some demonstrative embodiments, WM 103 may include a DMG channel. Inother embodiments, WM 103 may include any other additional oralternative directional channel.

In other embodiments, WM 103 may include any other type of channel overany other frequency band.

In some demonstrative embodiments, devices 102 and/or 140 may performthe functionality of one or more wireless stations, e.g., as describedbelow.

In some demonstrative embodiments, devices 102 and/or 140 may performthe functionality of one or more DMG stations.

In other embodiments, devices 102 and/or 140 may perform thefunctionality of any other wireless device and/or station, e.g., a WLANSTA, a WiFi STA, and the like.

In some demonstrative embodiments, devices 102 and/or 140 may includeone or more radios including circuitry and/or logic to perform wirelesscommunication between devices 102, 140 and/or one or more other wirelesscommunication devices. For example, device 102 may include a radio 114,and/or device 140 may include a radio 144.

In some demonstrative embodiments, radios 114 and/or 144 may include oneor more wireless receivers (Rx) including circuitry and/or logic toreceive wireless communication signals, RF signals, frames, blocks,transmission streams, packets, messages, data items, and/or data. Forexample, radio 114 may include a receiver 116, and/or radio 144 mayinclude a receiver 146.

In some demonstrative embodiments, radios 114 and/or 144 may include oneor more wireless transmitters (Tx) including circuitry and/or logic tosend wireless communication signals, RF signals, frames, blocks,transmission streams, packets, messages, data items, and/or data. Forexample, radio 114 may include a transmitter 118, and/or radio 144 mayinclude a transmitter 148.

In some demonstrative embodiments, radios 114 and/or 144 may includecircuitry, logic, modulation elements, demodulation elements,amplifiers, analog to digital and digital to analog converters, filters,and/or the like. For example, radios 114 and/or 144 may include or maybe implemented as part of a wireless Network Interface Card (NIC), andthe like.

In some demonstrative embodiments, radios 114 and/or 144 may include, ormay be associated with, one or more antennas 107 and/or 147,respectively.

In one example, device 102 may include a single antenna 107. In otherexample, device 102 may include two or more antennas 107.

In one example, device 140 may include a single antenna 147. In otherexample, device 140 may include two or more antennas 147.

Antennas 107 and/or 147 may include any type of antennas suitable fortransmitting and/or receiving wireless communication signals, blocks,frames, transmission streams, packets, messages and/or data. Forexample, antennas 107 and/or 147 may include any suitable configuration,structure and/or arrangement of one or more antenna elements,components, units, assemblies and/or arrays. Antennas 107 and/or 147 mayinclude, for example, antennas suitable for directional communication,e.g., using beamforming techniques. For example, antennas 107 and/or 147may include a phased array antenna, a multiple element antenna, a set ofswitched beam antennas, and/or the like. In some embodiments, antennas107 and/or 147 may implement transmit and receive functionalities usingseparate transmit and receive antenna elements. In some embodiments,antennas 107 and/or 147 may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements.

In some demonstrative embodiments, antennas 107 and/or 147 may include adirectional antenna, which may be steered to a plurality of beamdirections.

In some demonstrative embodiments, antennas 107 and/or 147 may include adirectional antenna, which may be steered to a plurality of beamdirections. For example, antenna 107 may be steered to a plurality ofbeam directions 135, and/or antenna 147 may be steered to a plurality ofbeam directions 145. For example, device 102 may transmit a directionaltransmission 139 to device 140, e.g., via a direction 133, and/or device140 may transmit a directional transmission 149 to device 102, e.g., viaa direction 143.

In some demonstrative embodiments, device 102 may include a controller124, and/or device 140 may include a controller 154. Controllers 124and/or 154 may be configured to perform one or more communications, maygenerate and/or communicate one or more messages and/or transmissions,and/or may perform one or more functionalities, operations and/orprocedures between devices 102 and/or 140 and/or one or more otherdevices, e.g., as described below.

In some demonstrative embodiments, controllers 124 and/or 154 mayinclude circuitry and/or logic, e.g., one or more processors includingcircuitry and/or logic, memory circuitry and/or logic, Media-AccessControl (MAC) circuitry and/or logic, Physical Layer (PHY) circuitryand/or logic, and/or any other circuitry and/or logic, configured toperform the functionality of controllers 124 and/or 154, respectively.Additionally or alternatively, one or more functionalities ofcontrollers 124 and/or 154 may be implemented by logic, which may beexecuted by a machine and/or one or more processors, e.g., as describedbelow.

In one example, controller 124 may include circuitry and/or logic, forexample, one or more processors including circuitry and/or logic, tocause a wireless device, e.g., device 102, and/or a wireless station,e.g., a wireless STA implemented by device 102, to perform one or moreoperations, communications and/or functionalities, e.g., as describedherein.

In one example, controller 154 may include circuitry and/or logic, forexample, one or more processors including circuitry and/or logic, tocause a wireless device, e.g., device 140, and/or a wireless station,e.g., a wireless STA implemented by device 140, to perform one or moreoperations, communications and/or functionalities, e.g., as describedherein.

In some demonstrative embodiments, device 102 may include a messageprocessor 128 configured to generate, process and/or access one ormessages communicated by device 102.

In one example, message processor 128 may be configured to generate oneor more messages to be transmitted by device 102, and/or messageprocessor 128 may be configured to access and/or to process one or moremessages received by device 102, e.g., as described below. In oneexample, message processor 128 may be configured to process transmissionof one or more messages from a wireless station, e.g., a wireless STAimplemented by device 102; and/or message processor 128 may beconfigured to process reception of one or more messages by a wirelessstation, e.g., a wireless STA implemented by device 102.

In some demonstrative embodiments, device 140 may include a messageprocessor 158 configured to generate, process and/or access one ormessages communicated by device 140.

In one example, message processor 158 may be configured to generate oneor more messages to be transmitted by device 140, and/or messageprocessor 158 may be configured to access and/or to process one or moremessages received by device 140, e.g., as described below. In oneexample, message processor 158 may be configured to process transmissionof one or more messages from a wireless station, e.g., a wireless STAimplemented by device 140; and/or message processor 158 may beconfigured to process reception of one or more messages by a wirelessstation, e.g., a wireless STA implemented by device 140.

In some demonstrative embodiments, message processors 128 and/or 158 mayinclude circuitry, e.g., processor circuitry, memory circuitry,Media-Access Control (MAC) circuitry, Physical Layer (PHY) circuitry,and/or any other circuitry, configured to perform the functionality ofmessage processors 128 and/or 158. Additionally or alternatively, one ormore functionalities of message processors 128 and/or 158 may beimplemented by logic, which may be executed by a machine and/or one ormore processors, e.g., as described below.

In some demonstrative embodiments, at least part of the functionality ofmessage processor 128 may be implemented as part of radio 114, and/or atleast part of the functionality of message processor 158 may beimplemented as part of radio 144.

In some demonstrative embodiments, at least part of the functionality ofmessage processor 128 may be implemented as part of controller 124,and/or at least part of the functionality of message processor 158 maybe implemented as part of controller 154.

In other embodiments, the functionality of message processor 128 may beimplemented as part of any other element of device 102, and/or thefunctionality of message processor 158 may be implemented as part of anyother element of device 140.

In some demonstrative embodiments, at least part of the functionality ofcontroller 124 and/or message processor 128 may be implemented by anintegrated circuit, for example, a chip, e.g., a System in Chip (SoC).In one example, the chip or SoC may be configured to perform one or morefunctionalities of radio 114. For example, the chip or SoC may includeone or more elements of controller 124, one or more elements of messageprocessor 128, and/or one or more elements of radio 114. In one example,controller 124, message processor 128, and radio 114 may be implementedas part of the chip or SoC.

In other embodiments, controller 124, message processor 128 and/or radio114 may be implemented by one or more additional or alternative elementsof device 102.

In some demonstrative embodiments, at least part of the functionality ofcontroller 154 and/or message processor 158 may be implemented by anintegrated circuit, for example, a chip, e.g., a SoC. In one example,the chip or SoC may be configured to perform one or more functionalitiesof radio 144. For example, the chip or SoC may include one or moreelements of controller 154, one or more elements of message processor158, and/or one or more elements of radio 144. In one example,controller 154, message processor 158, and radio 144 may be implementedas part of the chip or SoC.

In other embodiments, controller 154, message processor 158 and/or radio144 may be implemented by one or more additional or alternative elementsof device 140.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to perform the functionality of an access point (AP), e.g., aDMG AP, and/or a personal basic service set (PBSS) control point (PCP),e.g., a DMG PCP, for example, an AP/PCP STA, e.g., a DMG AP/PCP STA.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to perform the functionality of a non-AP STA, e.g., a DMGnon-AP STA, and/or a non-PCP STA, e.g., a DMG non-PCP STA, for example,a non-AP/PCP STA, e.g., a DMG non-AP/PCP STA.

In one example, a station (STA) may include a logical entity that is asingly addressable instance of a medium access control (MAC) andphysical layer (PHY) interface to the wireless medium (WM). The STA mayperform any other additional or alternative functionality.

In one example, an AP may include an entity that contains a station(STA), e.g., one STA, and provides access to distribution services, viathe wireless medium (WM) for associated STAs. The AP may perform anyother additional or alternative functionality.

In one example, a personal basic service set (PBSS) control point (PCP)may include an entity that contains a STA, e.g., one station (STA), andcoordinates access to the wireless medium (WM) by STAs that are membersof a PBSS. The PCP may perform any other additional or alternativefunctionality.

In one example, a PBSS may include a directional multi-gigabit (DMG)basic service set (BSS) that includes, for example, one PBSS controlpoint (PCP). For example, access to a distribution system (DS) may notbe present, but, for example, an intra-PBSS forwarding service mayoptionally be present.

In one example, a PCP/AP STA may include a station (STA) that is atleast one of a PCP or an AP. The PCP/AP STA may perform any otheradditional or alternative functionality.

In one example, a non-AP STA may include a STA that is not containedwithin an AP. The non-AP STA may perform any other additional oralternative functionality.

In one example, a non-PCP STA may include a STA that is not a PCP. Thenon-PCP STA may perform any other additional or alternativefunctionality.

In one example, a non PCP/AP STA may include a STA that is not a PCP andthat is not an AP. The non-PCP/AP STA may perform any other additionalor alternative functionality.

Some communications over a wireless communication band, for example, aDMG band or any other band, may be performed over a single channelbandwidth (BW). For example, the IEEE 802.11ad Specification defines a60 GHz system with a single channel bandwidth (BW) of 2.16 GHz, which isto be used by all Stations (STAs) for both transmission and reception.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to implement one or more mechanisms, which may, for example,enable to extend a single-channel BW scheme, e.g., a scheme inaccordance with the IEEE 802.11ad Specification or any other scheme, forhigher data rates and/or increased capabilities, e.g., as describedbelow.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to implement one or more channel bonding mechanisms, whichmay, for example, support communication over bonded channels.

In some demonstrative embodiments, the Channel bonding may include, forexample, a mechanism and/or an operation whereby two or more channelscan be combined, e.g., for a higher bandwidth of packet transmission,for example, to enable achieving higher data rates, e.g., when comparedto transmissions over a single channel.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to implement one or more channel bonding mechanisms, whichmay for example, support an increased channel bandwidth, for example, achannel BW of 4.32 GHz, a channel BW of 6.48 GHz, and/or any otheradditional or alternative channel BW.

Some specifications, e.g., an IEEE 802.11ad Specification, may beconfigured to support a Single User (SU) system, in which a Station(STA) cannot transmit frames to more than a single STA at a time. SuchSpecifications may not be able, for example, to support transmissionfrom a STA to multiple STAs simultaneously, for example, using amulti-user MIMO (MU-MIMO) scheme, e.g., a downlink (DL) MU-MIMO, or anyother MU scheme.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to implement one or more Multi-User (MU) mechanisms. Forexample, devices 102 and/or 140 may be configured to implement one ormore MU mechanisms, which may be configured to enable MU communication.

In one example, devices 102 and/or 140 may be configured to implementone or more MU mechanisms, which may be configured to enable, forexample, MU communication of Downlink (DL) frames using aMultiple-Input-Multiple-Output (MIMO) scheme, for example, between adevice, e.g., device 102, and a plurality of devices, e.g., includingdevice 140 and/or one or more other devices.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to implement any other additional or alternative MUmechanism, e.g., to communicated MU transmissions, and/or any other MIMOmechanism, e.g., to communicate MIMO transmissions.

In some demonstrative embodiments, a communication scheme may beconfigured to include changes to an existing standard, for example, alegacy standard, e.g., the IEEE 802.11ad standard, for example, in aPhysical layer (PHY) and/or a Media Access Control (MAC) layer, e.g., tosupport channel bonding and/or MU capabilities, e.g., as describedbelow.

In other embodiments, a new and/or independent communication scheme mayinclude a PHY layer and/or MAC layer and/or any other layer, which maybe configured to support channel bonding and/or MU capabilities, e.g.,as described below.

In some demonstrative embodiments, a configuration of a Physical Layer(PHY) header in accordance with the IEEE 802.11ad Specifications may notbe suitable, for example, at least to support MU capabilities and/orchannel bonding capabilities.

FIG. 2 is a schematic illustration of a Single Carrier (SC) PhysicalLayer (PHY) header 200. For example, the SC PHY header of FIG. 2 may becommunicated in accordance with the IEEE 802.11ad-2012 Specification.

In some demonstrative embodiments, header 200 may include a scramblerinitialization field 202, an MCS field 204, a length field 206, anAdditional PPDU field 208, a packet type field 210, a training lengthfield 212, an aggregation field 214, a beam tracking request field 216,a last Received Signal Strength Indication (RSSI) field 218, aturnaround field 220, a reserved field 222, and/or a Header CheckSequence (HCS) field 224. In other embodiments, header 200 may includeany other additional or alternative fields.

In some demonstrative embodiments, the PHY header according to the IEEE802.11ad-2012 Specification may not be capable, for example, of at leastindicating to multiple STAs to which STA a Physical Layer ConvergenceProtocol (PLCP) Protocol Data Unit (PPDU) is to be addressed, e.g., aspart of a MU transmission.

In some demonstrative embodiments, spatial streams of a transmission,for example a MU MIMO transmission, may be assigned to different STAs,for example, in opposed to the SU transmission supported by the IEEE802.11ad-2012 Specification.

Accordingly, in some demonstrative embodiments, additional signaling maybe configured, for example, to support transmission of spatial streamsto different STAs, e.g., as described below.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to use a header, for example, a PHY header, which may beconfigured to provide header signaling, e.g., PHY header signaling, forexample, modified, new, and/or enhanced header signaling, which may beconfigured to accommodate frame transmission to multiple stations, forexample, using DL MU MIMO, e.g., as described below.

In some demonstrative embodiments, the configuration of a header, forexample, a PHY header, may be enhanced, changed, updated, reconfigured,and/or amended, for example, to support MU capabilities and/or channelbonding capabilities.

In other embodiments, a header, e.g., a PHY header, of any otherSpecification may be enhanced, changed, and/or amended, and/or a newheader structure, e.g., a new PHY header structure, may be defined,e.g., as described below.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to communicate over a Next Generation 60 GHz (NG60) network,an Extended DMG (EDMG) network, and/or any other network over any otherfrequency band.

For example, devices 102 and/or 140 may be configured to communicate DLMU-MIMO transmissions and/or use channel bonding, for example, forcommunicating over the NG60 and/or EDMG networks.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to process transmission and/or reception of transmissionsincluding at least two headers (also referred to as “signal fields”),for example, two new headers,

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to process transmission and/or reception of transmissionsincluding at least one header, for example, at least one new header,e.g., in addition to an existing or legacy header.

In some demonstrative embodiments, the at least two new headers may beconfigured, for example, to support MU-MIMO signaling, correspondingtraining sequences, and/or any other functionality and/orcommunications, e.g., as described below.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to process signaling and/or indications in a header, forexample, a PHY header, e.g., to indicate the presence and format of theat least two headers.

In some demonstrative embodiments, a header of a frame, e.g., a PHYheader or any other header, may be configured according to a signalingscheme, for example, to indicate whether one or more additional headersare to be included within a PPDU, for example, to indicate MU-MIMOoperation and/or channel bonding, e.g., as described below.

In some demonstrative embodiments, controller 124 may be configured tocause a wireless station, for example, a wireless station implemented bydevice 102, to generate a frame including a header portion and a dataportion, e.g., as described below. For example, controller 124 may causemessage processor 128 and/or radio 114 to generate and/or transmit theframe.

In some demonstrative embodiments, controller 154 may be configured tocause a wireless station, for example, a wireless station implemented bydevice 140, to process a received frame including a header portion and adata portion, e.g., as described below. For example, controller 154 maycause message processor 158 and/or radio 114 to process reception of theframe.

In some demonstrative embodiments, the header portion may include, forexample, a PHY header, e.g., as described below.

In some demonstrative embodiments, the header portion may be configured,for example, to indicate whether or nor one or more headers are to beincluded within the header portion, for example, one or more headers toindicate a MU transmission, e.g., MU-MIMO operation, and/or channelbonding, e.g., as described below.

In some demonstrative embodiments, the header portion, for example, aPHY header, may be configured to use a channel bitmap, which may beconfigured, for example, to indicate a plurality of channels, forexample, a set of channels, e.g., contiguous and/or non-contiguouschannels, which may be bonded, for example, to communicate a PPDU (“thecurrent PPDU”) including the header portion, e.g., as described below.

In some demonstrative embodiments, the header portion, for example, aPHY header, may be configured to include a channel number correspondingto a primary channel that a Basic Service Set (BSS) may be currentlyoperating on. This configuration may enable, for example, to provide animplicit indication in the current PPDU of the number of contiguouschannels that are to be bonded, e.g., as described below.

Reference is made to FIG. 3, which schematically illustrates a framestructure 300, in accordance with some demonstrative embodiments.

In some demonstrative embodiments, device 102 (FIG. 1) and/or device 140(FIG. 1) may be configured to process transmission and/or reception ofthe frame structure 300 of FIG. 3. For example, device 102 (FIG. 1) maybe configured to generate and transmit a frame having the framestructure of FIG. 3, and/or device 140 (FIG. 1) may be configured toprocess reception of a frame having the frame structure of FIG. 3, e.g.,as described below.

In some demonstrative embodiments, as shown in FIG. 3, frame structure300 may include a Short Training Field (STF) 302, a channel estimation(CE) field 304, a header portion 306, a data portion 314, an AutomaticGain Control (AGC) field 316, and/or a Training (TRN) field 318.

In some demonstrative embodiments, header portion 306 may include a PHYheader portion.

In some demonstrative embodiments, header portion 306 may include a PLCPheader portion, e.g., of a PPDU including the fields of frame structure300.

In some demonstrative embodiments, a header structure of header portion306 may be configured to support NG60 and/or EDMG communication, and/orany other type and/or formal of communication, e.g., as described below.

In some demonstrative embodiments, as shown in FIG. 3, header portion306 may include legacy header 308.

In some demonstrative embodiments, legacy header 308 may include aheader, which may have a structure in accordance with a current, legacyand/or conventional header.

In some demonstrative embodiments, legacy header 308 may have astructure, which may be processed, decoded and/or demodulated by one ormore legacy, existing and/or conventional, e.g., devices which maycurrently be in the market.

In some demonstrative embodiments, legacy header 308 may have astructure, which may be in accordance with a PHY header structureaccording to an IEEE 802.11 Specification, for example, an IEEE 802.11adSpecification, and/or any other Specification, protocol or Standard.

In some demonstrative embodiments, legacy header 308 may include aSingle Carrier (SC) header. In other embodiments, legacy header 308 mayinclude an OFDM header, and/or any other header.

In some demonstrative embodiments, header portion 306 may be configuredto include one or more new information headers, which may be included aspart of a PLCP header of a PPDU, e.g., as described below

In some demonstrative embodiments, header portion 306 may include afirst non-legacy header 310, denoted “NG60 Header A” or “EDMG Header A”,e.g., as described below.

In some demonstrative embodiments, header portion 306 may include asecond non-legacy header 312, denoted “NG60 Header B” or “EDMG HeaderB”.

In some demonstrative embodiments, header portion 306 may optionallyinclude one or more additional non-legacy headers (not shown in FIG. 3).In one example, the additional non-legacy headers may include additionalinformation, e.g., in addition to the information described below withrespect to headers 310 and/or 312. In another example, at least part ofthe information described below with respect to headers 310 and/or 312may be included in, e.g., distributed between, more than two headers,e.g., headers 310, 312 and one or more additional headers.

In some demonstrative embodiments, non-legacy headers 310 and/or 312 maybe configured, for example, to allow, at least a modular design, e.g.,if not all features are to be supported by all devices.

In some demonstrative embodiments, non-legacy headers 310 and/or 312 maybe configured, for example, to enable, at least fit each of the firstand/or second non-legacy headers in a single PHY symbol/block size,which may be limited, for example, to a size of about 48 bits, e.g., ifSC is used, or any other size.

In other embodiments, two or more non-legacy headers, e.g., non-legacyheaders 310 and 312, may be combined into a single header and/or may bedivided into more than two headers.

In some demonstrative embodiments, non-legacy header 310 may include,for example, information of a number of channels to be bonded, e.g., totransmit at least data portion 314; modulation and coding informationfor example, an indication of a modulation and coding scheme (MCS),e.g., to be applied at least to data portion 314; a length of the PPDU,e.g., a length of at least data portion 314 and/or one or more elementsof frame 300, a Cyclic Prefix (CP) interval; a number of spatialstreams, e.g., to transmit at least data portion 314 to one or moreusers; and/or any other additional or alternative information.

In some demonstrative embodiments, non-legacy header 312 may include,for example, MU-MIMO parameters, e.g., only MU-MIMO parameters, forexample, information relating to Spatial Streams (SS), beamformingvariables, training sequences, e.g., to be applied to at least dataportion 314, and/or any other additional or alternative information.

In some demonstrative embodiments, at least some of the information ofnon-legacy header 312 may be included in non-legacy header 310, forexample, in addition to or instead of including the information innon-legacy header 312.

In one example, the non-legacy header 310 may include information of thenumber of spatial streams, e.g., to transmit at least data portion 314to one or more users.

In some demonstrative embodiments, a non-legacy header may be mandatoryor optional, e.g., as described below.

In some demonstrative embodiments, at least one non-legacy header, e.g.,non-legacy header 310, may be configured to always be present, forexample, in one or more types of frames or transmissions, for example,in all NG60 PPDUs and/or any other frames or transmissions.

In some demonstrative embodiments, at least one non-legacy header, e.g.,non-legacy header 312, may be configured to be optionally present, forexample, in one or more types of frames or transmissions, for example,in some or all NG60 PPDUs and/or any other frames or transmissions. Forexample, at least one non-legacy header, e.g., non-legacy header 312,may be present in one or more PPDUS, and absent from one or more otherPPDUs.

In some demonstrative embodiments, header portion 306 may be configuredto provide an indication on whether or not at least one non-legacyheader, e.g., non-legacy header 312, is to be included in a frame, e.g.,a PPDU including header portion 306, as described below.

In some demonstrative embodiments, the presence of absence of anon-legacy header, e.g., non-legacy header 312, in a PPDU may beindicated, for example, by an indication, for example, in a field, e.g.,a 1-bit field or any other field or indication, which may be, forexample, included in the PPDU.

In some demonstrative embodiments, the indication of the presence orabsence of the at least one non-legacy header may be included as part oflegacy header 308, e.g., as described below.

In some demonstrative embodiments, the indication of the presence orabsence of the at least one non-legacy header, e.g., non-legacy header312, may be included as part of another non-legacy header, for example,a mandatory non-legacy header or an optional non-legacy header. In oneexample, the indication of the presence or absence of the at least onenon-legacy header, e.g., non-legacy header 312, may be included as partof non-legacy header 310, e.g., as described below.

In other embodiments, the indication of the presence or absence of theat least one non-legacy header, e.g., non-legacy header 312, may beincluded as part of any other element of the frame structure 300.

In some demonstrative embodiments, header portion 306 may include afirst indication to indicate whether or not header portion 306 is toinclude non-legacy header 312, e.g., following non-legacy header 310;and/or a second indication to indicate whether or not channel bonding isto be used, for example, to communicate at least data portion 314, AGCfield 316 and/or TRN field 318, e.g., as described below.

In some demonstrative embodiments, legacy header 308 may include thefirst indication and/or the second indication, e.g., as described below.

In some demonstrative embodiments, legacy header 308 may include boththe first indication and the second indication, e.g., as describedbelow.

In some demonstrative embodiments, according to a first scheme (“Option1”), an indication and/or signaling of the presence of non-legacy header312, and/or an indication of channel bonding, may be included in legacyheader 308, e.g., as described below.

In some demonstrative embodiments, one or more bits of the legacy header308, for example, 2 bits in the legacy header 308, e.g., 2 Reserved bitsin the legacy header 308, or any other number of bits of legacy header308, may be re-used, for example, to provide the first indication and/orthe second indication.

In some demonstrative embodiments, a bit of legacy header 308, forexample, a reserved bit of legacy header 308, may be configured toindicate presence of non-legacy header 312, e.g., as described below.

In some demonstrative embodiments, a bit of legacy header 308, forexample, a reserved bit of legacy header 308, may be configured toindicate whether or not channel bonding is to be applied, for example,to communicate data portion 314, AGC field 316 and/or TRN field 318,e.g., as described below.

Reference is made to FIG. 4, which schematically illustrates a headerstructure 400, in accordance with some demonstrative embodiments. Forexample, devices 102 and/or 140 (FIG. 1) may be configured to processtransmission and/or reception of the header structure 400 of FIG. 4,e.g., in accordance with the Option 1 scheme.

In some demonstrative embodiments, legacy header 308 (FIG. 3) may havethe structure of header 400.

In some demonstrative embodiments, one or more fields of header 400 mayinclude one or more fields of a legacy header structure, for example, inaccordance with an IEEE 802.11 Specification, e.g., the IEEE802.11ad-2012 Specification, and/or any other specification, standardand/or protocol. In one example, the structure of header 400 may be ionaccordance with the structure of header 200 (FIG. 2).

In some demonstrative embodiments, header 400 may include a scramblerinitialization field 402, an MCS field 404, a length field 406, anAdditional PPDU field 408, a packet type field 410, a training lengthfield 412, an aggregation field 414, a beam tracking request field 416,a last Received Signal Strength Indication (RSSI) field 418, aturnaround field 420, a reserved field 422, and/or a Header CheckSequence (HCS) field 424. In other embodiments, header 400 may includeany other additional or alternative fields.

In some demonstrative embodiments, as shown in FIG. 4, reserved field422 may include four reserved bits. In other embodiments, reserved field422 may include any other number of reserved bits.

In some demonstrative embodiments, a reserved bit 430 of reserved field422 may be configured as an indication bit (“NG60 Header B Presence”subfield) to indicate, for example, whether or not a non-legacy header,e.g., non-legacy header 312 (FIG. 3), is to be included in a headerportion, e.g., header portion 306 (FIG. 3), including header 400.

In some demonstrative embodiments, a wireless station, for example, awireless station implemented by device 102 (FIG. 1), which is togenerate and/or transmit a PPDU, e.g., according to frame structure 300(FIG. 3), may be configured to set bit 430 to a first value, e.g., 1,for example, to indicate that a non-legacy header, e.g., non-legacyheader 312 (FIG. 3), is to be included in the header of the PPDU, e.g.,in header portion 306 (FIG. 3).

In some demonstrative embodiments, a wireless station, for example, thewireless station implemented by device 102 (FIG. 1), which is togenerate and/or transmit a PPDU, e.g., according to frame structure 300(FIG. 3), may be configured to set bit 430 to a second value, e.g., 0,for example, to indicate that a non-legacy header, e.g., non-legacyheader 312 (FIG. 3), is not to be included in the header of the PPDU,e.g., in header portion 306 (FIG. 3).

In some demonstrative embodiments, a reserved bit 432 of reserved field422 may be configured as an indication bit (“Channel bonding” subfield)to indicate, for example, whether or not channel bonding is to beapplied to a transmission of at least a portion of a frame includingheader 400.

In some demonstrative embodiments, Channel Bonding subfield 432 may beconfigured to provide an indication of channel bonding with respect to 2or more channels. For example, the Channel Bonding subfield 432 may beconfigured to indicate whether channel bonding is assumed for thecurrent operation or transmission of the PPDU including header 400.

In some demonstrative embodiments, a wireless station, for example, awireless station implemented by device 102 (FIG. 1), which is togenerate and/or transmit a PPDU, e.g., according to frame structure 300(FIG. 3), may be configured to set bit 432 to a first value, e.g., 1,for example, to indicate that channel bonding is to be applied tocommunicate one or more portions of the PPDU, e.g., at least dataportion 314 (FIG. 3), AGC field 316 (FIG. 3), and/or TRN field 318 (FIG.3).

In some demonstrative embodiments, a wireless station, for example, awireless station implemented by device 102 (FIG. 1), which is togenerate and/or transmit a PPDU, e.g., according to frame structure 300(FIG. 3), may be configured to set bit 432 to a second value, e.g., 0,for example, to indicate that channel bonding is not to be applied tocommunicate one or more portions of the PPDU, e.g., at least dataportion 314 (FIG. 3), AGC field 316 (FIG. 3) and/or TRN field 318 (FIG.3).

In some demonstrative embodiments, a wireless station, for example, awireless station implemented by device 102 (FIG. 1), which is togenerate and/or transmit a PPDU, e.g., according to frame structure 300(FIG. 3), may be configured to set the values in both subfields 430 and432 to “1”, for example, to indicate that the header of the PPDU, e.g.,header portion 306, is to include a non-legacy header, e.g., non-legacyheader 312 (FIG. 3), and that channel bonding is to be applied tocommunicate one or more portions of the PPDU, e.g., at least dataportion 314 (FIG. 3, AGC field 316 (FIG. 3) and/or TRN field 318 (FIG.3).

Referring back to FIG. 3, in some demonstrative embodiments, non-legacyheader 310 may include the first indication and/or the secondindication, e.g., as described below.

In some demonstrative embodiments, non-legacy header 310 may includeboth the first indication and the second indication, e.g., as describedbelow.

In some demonstrative embodiments, according to a second scheme (“Option2”), an indication and/or signaling of the presence of non-legacy header312, and/or an indication of channel bonding, may be included innon-legacy header 310, e.g., as described below.

In some demonstrative embodiments, including in non-legacy header 310the indication of whether or not non-legacy header 312 is present inheader portion 306 may be advantageous, for example, by enabling toavoid a modification of legacy header 308.

Reference is made to FIG. 5, which schematically illustrates subfieldsof a non-legacy header 502 in a frame structure 500, in accordance withsome demonstrative embodiments. For example, devices 102 and/or 140(FIG. 1) may be configured to process transmission and/or reception ofthe header structure 500 of FIG. 5, e.g., in accordance with the Option2 scheme.

In some demonstrative embodiments, frame structure 500 may one or moreof the fields of frame structure 300 (FIG. 3), e.g., as described above.

In some demonstrative embodiments, non-legacy header 310 (FIG. 3) mayinclude, for example, one or more of the subfields of non-legacy header502.

In some demonstrative embodiments, non-legacy header 502 may include anindication subfield (“NG60 Header B Presence” subfield) 530, e.g.,including one bit, to indicate, for example, whether or not a non-legacyheader 504, e.g., non-legacy header 312 (FIG. 3), is to be included in aheader portion 508, e.g., header portion 306 (FIG. 3), of frame 500.

In some demonstrative embodiments, a wireless station, for example, awireless station implemented by device 102 (FIG. 1), which is togenerate and/or transmit a PPDU, e.g., according to frame structure 500,may be configured to set subfield 530 to a first value, e.g., 1, forexample, to indicate that non-legacy header 504, e.g., non-legacy header312 (FIG. 3), is to be included in header portion 508, e.g., in headerportion 306 (FIG. 3).

In some demonstrative embodiments, a wireless station, for example, awireless station implemented by device 102 (FIG. 1), which is togenerate and/or transmit a PPDU, e.g., according to frame structure 500,may be configured to set subfield 530 to a second value, e.g., 0, forexample, to indicate that non-legacy header 504, e.g., non-legacy header312 (FIG. 3), is not to be included in header portion 508, e.g., inheader portion 306 (FIG. 3).

In some demonstrative embodiments, non-legacy header 502 may include anindication subfield (“Channel bonding” subfield) 532, e.g., includingone bit, to indicate, for example, whether or not channel bonding is tobe applied to a transmission of one or more portions of frame 500, forexample, a data portion 514, an AGC field 516, and/or a TRN field 518.

In some demonstrative embodiments, Channel Bonding subfield 532 may beconfigured to provide an indication of channel bonding with respect totwo or more channels. For example, the Channel Bonding subfield 532 maybe configured to indicate whether channel bonding is assumed for thecurrent operation or transmission of one or more portions of frame 500,for example, data portion 514, AGC field 516, and/or TRN field 518.

In some demonstrative embodiments, a wireless station, for example, awireless station implemented by device 102 (FIG. 1), which is togenerate and/or transmit a PPDU, e.g., according to frame structure 500,may be configured to set subfield 532 to a first value, e.g., 1, forexample, to indicate that channel bonding is to be applied tocommunicate one or more portions of the PPDU, e.g., at least dataportion 514, AGC field 516, and/or TRN field 518.

In some demonstrative embodiments, a wireless station, for example, awireless station implemented by device 102 (FIG. 1), which is togenerate and/or transmit a PPDU, e.g., according to frame structure 500,may be configured to set subfield 532 to a second value, e.g., 0, forexample, to indicate that channel bonding is not to be applied tocommunicate one or more portions of the PPDU, e.g., at least dataportion 514, AGC field 516, and/or TRN field 518.

In some demonstrative embodiments, a wireless station, for example, awireless station implemented by device 102 (FIG. 1), which is togenerate and/or transmit a PPDU, e.g., according to frame structure 500,may be configured to set the values in both subfields 530 and 532 to“1”, for example, to indicate that the header of the PPDU, e.g., headerportion 508, is to include a non-legacy header, e.g., non-legacy header504, and that channel bonding is to be applied to communicate one ormore portions of the PPDU, e.g., at least data portion 514, AGC field516, and/or TRN field 518.

Referring back to FIG. 3, in some demonstrative embodiments, headerportion 506 may be configured to include an indication of two or morechannels to be bonded, for example, if channel bonding is to be used,e.g., as described below.

In some demonstrative embodiments, devices 102 and/or 140 (FIG. 1) maybe configured to process reception and/or transmission of the indicationof the channels to be bonded, for example, if channel bonding is to beused, e.g., as described below.

In some demonstrative embodiments, header portion 306 may be configuredto include the indication of the channels to be bonded, for example, incase the Channel Bonding subfield, e.g., subfield 432 (FIG. 3) orsubfield 532 (FIG. 5), includes a value, e.g., “1”, to indicate thatchannel bonding is to be used.

In some demonstrative embodiments, the indication of the channels to bebonded may provide, for example, a least an indication with respect tothe number of channels that are to be bonded, e.g., to obtain thebandwidth of an operating channel.

In some demonstrative embodiments, the indication of two or morechannels to be bonded may be included in a non-legacy header, forexample, non-legacy header 310, e.g., as described below.

In other embodiments, the indication of two or more channels to bebonded may be included in any other non-legacy header, in any otherelement of header portion 306, and/or in any other element of frame 300.

In some demonstrative embodiments, according to a first scheme (“OptionA”), non-legacy header 310 may include a Channel Bitmap field 360, forexample, if channel bonding is to be applied.

In some demonstrative embodiments, channel bitmap field 360 may beincluded in non-legacy header 310, for example, when the Channel Bondingsubfield, e.g., subfield 432 (FIG. 3) or subfield 532 (FIG. 5), includesa value, e.g., “1”, to indicate that channel bonding is to be used.

In some demonstrative embodiments, channel bitmap field 360 may beabsent from non-legacy header 310, for example, when the Channel Bondingsubfield, e.g., subfield 432 (FIG. 3) or subfield 532 (FIG. 5), includesa value, e.g., “0”, to indicate that channel bonding is not to be used.

In some demonstrative embodiments, channel bitmap field 360 may include,for example, 1 bit octet, e.g., corresponding to eight channels, or anyother number of bits corresponding to any other number of channels.

In some demonstrative embodiments, channel bitmap field 360 may includea sequence of a plurality of bits corresponding to a respectiveplurality of channels. For example, a bit of the sequence of bits may beset to have a value to indicate whether or not a respective channel ofthe plurality of channels is to be bonded.

In some demonstrative embodiments, a bit in the channel bitmap 360,e.g., each bit in the bitmap 360, may be configured to represent onechannel.

In some demonstrative embodiments, a wireless station, for example, awireless station implemented by device 102 (FIG. 1), which is togenerate and/or transmit a PPDU, e.g., according to frame structure 300,may be configured to set a value in a bit location of bitmap 360 toindicate whether or not a channel corresponding to the bit location isto be bonded.

In some demonstrative embodiments, a wireless station, for example, awireless station implemented by device 102 (FIG. 1), which is togenerate and/or transmit a PPDU, e.g., according to frame structure 300,may be configured to set the bit location of bitmap 360 to a firstvalue, e.g., “1”, to indicate that the channel corresponding to the bitlocation is to be bonded.

In some demonstrative embodiments, a wireless station, for example, awireless station implemented by device 102 (FIG. 1), which is togenerate and/or transmit a PPDU, e.g., according to frame structure 300,may be configured to set the bit location of bitmap 360 to a secondvalue, e.g., “0”, to indicate that the channel corresponding to the bitlocation is not to be bonded.

In one example, a wireless station, for example, a wireless stationimplemented by device 102 (FIG. 1), which is to generate and/or transmita PPDU, e.g., according to frame structure 300, may be configured to seta sequence of “10000001” in the Channel Bitmap 360, for example, toindicate that the first and eighth channels are to be bonded.

In some demonstrative embodiments, the channel bitmap field 360 may beconfigured to enable, for example, bonding of two or more contiguouschannels and/or two or more non-contiguous channels.

In some demonstrative embodiments, according to a second scheme (“OptionB”), non-legacy header 360 may include one or more information fields,for example, a primary channel field 370 and/or a channel bandwidth(CH_BW) field 372, for example, if channel bonding is to be applied.

In some demonstrative embodiments, primary channel field 370 and/orchannel BW field 372 may be included in non-legacy header 310, forexample, when the Channel Bonding subfield, e.g., subfield 432 (FIG. 3)or subfield 532 (FIG. 5), includes a value, e.g., “1”, to indicate thatchannel bonding is to be used.

In some demonstrative embodiments, primary channel field 370 and/orchannel BW field 372 may be absent from non-legacy header 310, forexample, when the Channel Bonding subfield, e.g., subfield 432 (FIG. 3)or subfield 532 (FIG. 5), includes a value, e.g., “0”, to indicate thatchannel bonding is not to be used.

In some demonstrative embodiments, a CH_BW field 372 may be configuredto indicate a bandwidth of a bonded channel

In some demonstrative embodiments, a Primary Channel field 370 may beconfigured, for example, to indicate a primary channel of two or morechannels to be bonded.

In some demonstrative embodiments, primary channel field 370 mayinclude, for example, a channel number corresponding to a primarychannel, for example, that a BSS may be currently operating on, or anyother primary channel of a network.

In some demonstrative embodiments, a CH_BW field 372 may be configured,for example, to indicate a number of contiguous channels to be bonded.

For example, a receiving STA, e.g., device 140 (FIG. 1), which receivesa transmission, e.g., frame 300, including the CH_BW field 372, may beconfigured to determine a number of channels to be bonded, for example,by dividing the value in the CH_BW field 372 by a bandwidth value of asingle channel bandwidth, for example, a predefined channel bandwidth,e.g., as may be used in a NG60 network or in any other network. Thenumber obtained as a result of the division may be the number ofchannels to be bonded. For example, the result of dividing the value inthe CH_BW field 362 by the value of a single channel bandwidth may bethe number of secondary channels to be bonded, e.g., starting from (andincluding), a primary channel indicated by the Primary Channel field370.

In some demonstrative embodiments, the Option B scheme may beapplicable, for example, for contiguous channel bonding.

Referring back to FIG. 1, in some demonstrative embodiments, controller124 may be configured to cause a wireless station, for example, awireless station implemented by device 102, to generate a frameincluding a header portion, the header portion including a legacyheader, followed by a first non-legacy header, e.g., in accordance withthe structure of frame 300 (FIG. 3). For example, controller 124 maycause message processor 128 to generate the frame including headerportion 306 (FIG. 3), which may include legacy header 308 (FIG. 3)followed by non-legacy header 310 (FIG. 3).

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to generate the header portion including afirst indication to indicate whether or not the header portion is toinclude a second non-legacy header following the first non-legacyheader. For example, controller 124 may cause message processor 128 togenerate header portion 306 (FIG. 3) including the indication of whetheror not non-legacy header 312 (FIG. 3) is to be included in headerportion 306 (FIG. 3).

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to include subfield 430 (FIG. 3), e.g., inreserved field 422 (FIG. 4) of legacy header 308 (FIG. 3); or to includesubfield 530 (FIG. 5) in non-legacy header 502 (FIG. 5), e.g., asdescribed above.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to generate the header portion including asecond indication to indicate whether or not channel bonding is to beused. For example, controller 124 may cause message processor 128 togenerate header portion 306 (FIG. 3) including the indication of whetheror not channel bonding is to be used to communicate at least a portionof frame 300 (FIG. 3).

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to include subfield 432 (FIG. 3), e.g., inreserved field 422 (FIG. 4) of legacy header 308 (FIG. 3); or to includesubfield 532 (FIG. 5) in non-legacy header 502 (FIG. 5), e.g., asdescribed above.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to include in the first non-legacy header achannel bitmap to indicate two or more channels to be bonded, forexample, when the second indication is to indicate channel bonding is tobe used. For example, controller 124 may cause message processor 128 togenerate non-legacy header 310 (FIG. 3) including bitmap field 360 (FIG.3), for example, when subfield 430 (FIG. 4) is set to “1”, or whensubfield 530 (FIG. 5) is set to “1”.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to include in the first non-legacy header afirst field to indicate a primary channel to be used for channelbonding, and a second field to indicate a channel bandwidth to be usedfor the channel bonding, for example, when the second indication is toindicate channel bonding is to be used. For example, controller 124 maycause message processor 128 to generate non-legacy header 310 (FIG. 3)including field 370 (FIG. 3) and/or field 372 (FIG. 3), for example,when subfield 432 (FIG. 4) is set to “1”, or when subfield 532 (FIG. 5)is set to “1”.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to process transmission of the frame to atleast one second wireless station over a directional wirelesscommunication band. For example, controller 124 may cause messageprocessor 128 and/or radio 114 to process transmission of frame 300(FIG. 3) to at least one second wireless station, e.g., the wirelessstation implemented by device 140 and/or one or more other wirelessstations.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to transmit at least a data portion of theframe over a bonded channel, when the second indication is to indicatechannel bonding is to be used. For example, controller 124 may causeradio 114 to transmit at least data portion 314 (FIG. 3) over the bondedchannel, for example, when subfield 432 (FIG. 4) is set to “1”, or whensubfield 532 (FIG. 5) is set to “1”.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to transmit at least a data portion of theframe according to one or more parameters in the first non-legacyheader. For example, controller 124 may cause radio 114 to transmit atleast data portion 314 (FIG. 3) according to one or more of theparameters in non-legacy header 310 (FIG. 3).

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to transmit at least a data portion of theframe to a plurality of users, e.g., according to one or more MU-MIMOparameters in the second non-legacy header, for example, when the headerportion is to include the second non-legacy header. For example,controller 124 may cause radio 114 to transmit at least data portion 314(FIG. 3) according to one or more of the parameters in non-legacy header312 (FIG. 3), for example, when subfield 430 (FIG. 4) is set to “1”, orwhen subfield 530 (FIG. 5) is set to “1”.

In some demonstrative embodiments, controller 154 may be configured tocause a wireless station, for example, a wireless station implemented bydevice 140, to process reception of a frame (“the received frame”)including a header portion, the header portion including a legacyheader, followed by a first non-legacy header, e.g., in accordance withthe structure of frame 300 (FIG. 3). For example, controller 154 maycause message processor 158 to process reception of the frame includingheader portion 306 (FIG. 3), which may include legacy header 308 (FIG.3) followed by non-legacy header 310 (FIG. 3).

In one example, the received frame may include the frame transmitted bydevice 102.

In some demonstrative embodiments, controller 154 may be configured tocause the wireless station to process reception of at least a dataportion of the frame based at least on the first non-legacy header.

In some demonstrative embodiments, controller 154 may be configured tocause the wireless station to process reception of at least a dataportion of the frame over a bonded channel, when the second indicationis to indicate channel bonding is to be used. For example, controller154 may cause radio 144 and/or message processor 158 to processreception of at least data portion 314 (FIG. 3) over the bonded channel,for example, when subfield 432 (FIG. 4) is set to “1”, or when subfield532 (FIG. 5) is set to “1”.

In some demonstrative embodiments, controller 154 may be configured tocause the wireless station to process reception of at least a dataportion of the frame according to one or more parameters in the firstnon-legacy header. For example, controller 154 may cause radio 144and/or message processor 158 to process reception of at least dataportion 314 (FIG. 3) according to one or more of the parameters innon-legacy header 310 (FIG. 3).

In some demonstrative embodiments, controller 154 may be configured tocause the wireless station to process reception of at least a dataportion of the frame according to one or more MU-MIMO parameters in thesecond non-legacy header, for example, when the header portion is toinclude the second non-legacy header. For example, controller 154 maycause radio 144 and/or message processor 158 to process reception of atleast data portion 314 (FIG. 3) according to one or more of theparameters in non-legacy header 312 (FIG. 3), for example, when subfield430 (FIG. 4) is set to “1”, or when subfield 530 (FIG. 5) is set to “1”.

Reference is made to FIG. 6, which schematically illustrates a method ofcommunicating a wireless communication frame, in accordance with somedemonstrative embodiments. For example, one or more of the operations ofthe method of FIG. 5 may be performed by one or more elements of asystem, e.g., system 100 (FIG. 1), for example, one or more wirelessdevices, e.g., device 102 (FIG. 1) and/or device 140 (FIG. 1), acontroller, e.g., controller 124 (FIG. 1) and/or controller 154 (FIG.1), a radio, e.g., radio 114 (FIG. 1) and/or radio 144 (FIG. 1), and/ora message processor, e.g., message processor 128 (FIG. 1) and/or messageprocessor 158 (FIG. 1).

As indicated at block 602, the method may include generating a frameincluding a header portion, the header portion including a legacyheader, followed by a first non-legacy header, the header portionincluding a first indication to indicate whether or not the headerportion is to include a second non-legacy header following the firstnon-legacy header, the header portion including a second indication toindicate whether or not channel bonding is to be used. For example,controller 124 (FIG. 1) may cause message processor 128 (FIG. 1) togenerate frame 300 (FIG. 3) including header portion 306 (FIG. 3), e.g.,as described above.

As indicated at block 604, the method may include processingtransmission of the frame to at least one second wireless station over adirectional wireless communication band. For example, controller 124(FIG. 1) may cause message processor 128 (FIG. 1) and/or radio 114(FIG. 1) to process transmission of frame 300 (FIG. 3) to at least onesecond wireless station via a directional band, for example, a DMG band,e.g., as described above.

As indicated at block 606, the method may include processing receptionof a header portion of the frame. For example, controller 154 (FIG. 1)may cause message processor 158 (FIG. 1) and/or radio 144 (FIG. 1) toprocess reception of the header portion 306 (FIG. 3) of the frame 300(FIG. 3), e.g., as described above.

As indicated at block 608 the method may include processing reception ofat least a data portion of the frame based at least on the firstnon-legacy header. For example, controller 154 (FIG. 1) may causemessage processor 158 (FIG. 1) and/or radio 144 (FIG. 1) to processreception of at least data portion 314 (FIG. 3) of the frame 300 (FIG.3), for example, based at least one non-legacy header 310 (FIG. 3),e.g., as described above.

Reference is made to FIG. 7, which schematically illustrates a productof manufacture 700, in accordance with some demonstrative embodiments.Product 700 may include a non-transitory machine-readable storage medium702 to store logic 704, which may be used, for example, to perform atleast part of the functionality of devices 102 and/or 140 (FIG. 1),transmitters 118 and/or 148 (FIG. 1), receivers 116 and/or 146 (FIG. 1),controllers 124 and/or 154 (FIG. 1), message processors 128 (FIG. 1)and/or 158 (FIG. 1), and/or to perform one or more operations and/orfunctionalities, for example, one or more operations of the method ofFIG. 6. The phrase “non-transitory machine-readable medium” is directedto include all computer-readable media, with the sole exception being atransitory propagating signal.

In some demonstrative embodiments, product 700 and/or machine-readablestorage medium 702 may include one or more types of computer-readablestorage media capable of storing data, including volatile memory,non-volatile memory, removable or non-removable memory, erasable ornon-erasable memory, writeable or re-writeable memory, and the like. Forexample, machine-readable storage medium 702 may include, RAM, DRAM,Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM,programmable ROM (PROM), erasable programmable ROM (EPROM), electricallyerasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), CompactDisk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory(e.g., NOR or NAND flash memory), content addressable memory (CAM),polymer memory, phase-change memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppydisk, a hard drive, an optical disk, a magnetic disk, a card, a magneticcard, an optical card, a tape, a cassette, and the like. Thecomputer-readable storage media may include any suitable media involvedwith downloading or transferring a computer program from a remotecomputer to a requesting computer carried by data signals embodied in acarrier wave or other propagation medium through a communication link,e.g., a modem, radio or network connection.

In some demonstrative embodiments, logic 704 may include instructions,data, and/or code, which, if executed by a machine, may cause themachine to perform a method, process and/or operations as describedherein. The machine may include, for example, any suitable processingplatform, computing platform, computing device, processing device,computing system, processing system, computer, processor, or the like,and may be implemented using any suitable combination of hardware,software, firmware, and the like.

In some demonstrative embodiments, logic 704 may include, or may beimplemented as, software, a software module, an application, a program,a subroutine, instructions, an instruction set, computing code, words,values, symbols, and the like. The instructions may include any suitabletype of code, such as source code, compiled code, interpreted code,executable code, static code, dynamic code, and the like. Theinstructions may be implemented according to a predefined computerlanguage, manner or syntax, for instructing a processor to perform acertain function. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, such as C, C++, Java, BASIC, Matlab,Pascal, Visual BASIC, assembly language, machine code, and the like.

Examples

The following examples pertain to further embodiments.

Example 1 includes an apparatus comprising circuitry configured to causea first wireless station to generate a frame comprising a headerportion, the header portion comprising a legacy header, followed by afirst non-legacy header, the header portion comprising a firstindication to indicate whether or not the header portion is to comprisea second non-legacy header following the first non-legacy header, theheader portion comprising a second indication to indicate whether or notchannel bonding is to be used; and process transmission of the frame toat least one second wireless station over a directional wirelesscommunication band.

Example 2 includes the subject matter of Example 1, and optionally,wherein the legacy header comprises the first and second indications.

Example 3 includes the subject matter of Example 1, and optionally,wherein the first non-legacy header comprises the first and secondindications.

Example 4 includes the subject matter of any one of Examples 1-3, andoptionally, wherein the first non-legacy header comprises a channelbitmap to indicate two or more channels to be bonded, when the secondindication is to indicate channel bonding is to be used.

Example 5 includes the subject matter of Example 4, and optionally,wherein the channel bitmap comprises a sequence of a plurality of bitscorresponding to a respective plurality of channels, a bit of thesequence of bits having a value to indicate whether or not a respectivechannel of the plurality of channels is to be bonded.

Example 6 includes the subject matter of Example 5, and optionally,wherein two non-consecutive bits of the sequence of bits have a value toindicate that two non-contiguous channels are to be bonded.

Example 7 includes the subject matter of any one of Examples 1-3, andoptionally, wherein the first non-legacy header comprises a first fieldto indicate a primary channel to be used for channel bonding, and asecond field to indicate a channel bandwidth to be used for the channelbonding.

Example 8 includes the subject matter of any one of Examples 1-7, andoptionally, configured to cause the first wireless station to transmitat least a data portion of the frame over a bonded channel, when thesecond indication is to indicate channel bonding is to be used.

Example 9 includes the subject matter of any one of Examples 1-8, andoptionally, wherein the first non-legacy header comprises one or moreparameters selected from the group consisting of a number of channels tobe bonded, a modulation and coding scheme, a length of at least a dataportion of the frame, a Cyclic Prefix (CP) interval, and a number ofspatial streams.

Example 10 includes the subject matter of Example 9, and optionally,configured to cause the first wireless station to transmit at least thedata portion of the frame according to the one or more parameters.

Example 11 includes the subject matter of any one of Examples 1-10, andoptionally, wherein the header portion is to comprise the secondnon-legacy header, the second non-legacy header comprising one or moreMulti-User (MU) Multi-Input-Multi-Output (MIMO) (MU-MIMO) parameters.

Example 12 includes the subject matter of Example 11, and optionally,configured to cause the first wireless station to transmit at least adata portion of the frame to a plurality of users according to theMU-MIMO parameters.

Example 13 includes the subject matter of any one of Examples 1-12, andoptionally, wherein the legacy header comprises a Single Carrier (SC)header.

Example 14 includes the subject matter of any one of Examples 1-13, andoptionally, wherein the directional wireless communication band is aDirectional Multi-Gigabit (DMG) band.

Example 15 includes the subject matter of any one of Examples 1-14, andoptionally, wherein the first wireless station is a DirectionalMulti-Gigabit (DMG) Station (STA).

Example 16 includes the subject matter of any one of Examples 1-15, andoptionally, comprising a radio to transmit the frame.

Example 17 includes the subject matter of any one of Examples 1-16, andoptionally, comprising one or more directional antennas, a memory, and aprocessor.

Example 18 includes an apparatus comprising circuitry configured tocause a first wireless station to process reception of a header portionof a frame from a second wireless station over a directional wirelesscommunication band, the header portion comprising a legacy header,followed by a first non-legacy header, the header portion comprising afirst indication to indicate whether or not the header portion is tocomprise a second non-legacy header following the first non-legacyheader, the header portion comprising a second indication to indicatewhether or not channel bonding is to be used; and process reception ofat least a data portion of the frame based at least on the firstnon-legacy header.

Example 19 includes the subject matter of Example 18, and optionally,wherein the legacy header comprises the first and second indications.

Example 20 includes the subject matter of Example 18, and optionally,wherein the first non-legacy header comprises the first and secondindications.

Example 21 includes the subject matter of any one of Examples 18-20, andoptionally, wherein the first non-legacy header comprises a channelbitmap to indicate two or more channels to be bonded, when the secondindication is to indicate channel bonding is to be used.

Example 22 includes the subject matter of Example 21, and optionally,wherein the channel bitmap comprises a sequence of a plurality of bitscorresponding to a respective plurality of channels, a bit of thesequence of bits having a value to indicate whether or not a respectivechannel of the plurality of channels is to be bonded.

Example 23 includes the subject matter of Example 22, and optionally,wherein two non-consecutive bits of the sequence of bits have a value toindicate that two non-contiguous channels are to be bonded.

Example 24 includes the subject matter of any one of Examples 18-20, andoptionally, wherein the first non-legacy header comprises a first fieldto indicate a primary channel to be used for channel bonding, and asecond field to indicate a channel bandwidth to be used for the channelbonding.

Example 25 includes the subject matter of any one of Examples 18-24, andoptionally, configured to cause the first wireless station to processreception of at least the data portion of the frame over a bondedchannel, when the second indication is to indicate channel bonding is tobe used.

Example 26 includes the subject matter of any one of Examples 18-25, andoptionally, wherein the first non-legacy header comprises one or moreparameters selected from the group consisting of a number of channels tobe bonded, a modulation and coding scheme, a length of at least a dataportion of the frame, a Cyclic Prefix (CP) interval, and a number ofspatial streams.

Example 27 includes the subject matter of Example 26, and optionally,configured to cause the first wireless station to process reception ofat least the data portion of the frame according to the one or moreparameters.

Example 28 includes the subject matter of any one of Examples 18-27, andoptionally, wherein the header portion is to comprise the secondnon-legacy header, the second non-legacy header comprising one or moreMulti-User (MU) Multi-Input-Multi-Output (MIMO) (MU-MIMO) parameters.

Example 29 includes the subject matter of Example 28, and optionally,configured to cause the first wireless station to process reception ofat least the data portion of the frame according to the MU-MIMOparameters.

Example 30 includes the subject matter of any one of Examples 18-29, andoptionally, wherein the legacy header comprises a Single Carrier (SC)header.

Example 31 includes the subject matter of any one of Examples 18-30, andoptionally, wherein the directional wireless communication band is aDirectional Multi-Gigabit (DMG) band.

Example 32 includes the subject matter of any one of Examples 18-31, andoptionally, wherein the first wireless station is a DirectionalMulti-Gigabit (DMG) Station (STA).

Example 33 includes the subject matter of any one of Examples 18-32, andoptionally, comprising a radio to receive the frame.

Example 34 includes the subject matter of any one of Examples 18-33, andoptionally, comprising one or more directional antennas, a memory, and aprocessor.

Example 35 includes a method to be performed at a first wirelessstation, the method comprising generating a frame comprising a headerportion, the header portion comprising a legacy header, followed by afirst non-legacy header, the header portion comprising a firstindication to indicate whether or not the header portion is to comprisea second non-legacy header following the first non-legacy header, theheader portion comprising a second indication to indicate whether or notchannel bonding is to be used; and processing transmission of the frameto at least one second wireless station over a directional wirelesscommunication band.

Example 36 includes the subject matter of Example 35, and optionally,wherein the legacy header comprises the first and second indications.

Example 37 includes the subject matter of Example 35, and optionally,wherein the first non-legacy header comprises the first and secondindications.

Example 38 includes the subject matter of any one of Examples 35-37, andoptionally, wherein the first non-legacy header comprises a channelbitmap to indicate two or more channels to be bonded, when the secondindication is to indicate channel bonding is to be used.

Example 39 includes the subject matter of Example 38, and optionally,wherein the channel bitmap comprises a sequence of a plurality of bitscorresponding to a respective plurality of channels, a bit of thesequence of bits having a value to indicate whether or not a respectivechannel of the plurality of channels is to be bonded.

Example 40 includes the subject matter of Example 39, and optionally,wherein two non-consecutive bits of the sequence of bits have a value toindicate that two non-contiguous channels are to be bonded.

Example 41 includes the subject matter of any one of Examples 35-37, andoptionally, wherein the first non-legacy header comprises a first fieldto indicate a primary channel to be used for channel bonding, and asecond field to indicate a channel bandwidth to be used for the channelbonding.

Example 42 includes the subject matter of any one of Examples 35-41, andoptionally, comprising transmitting at least a data portion of the frameover a bonded channel, when the second indication is to indicate channelbonding is to be used.

Example 43 includes the subject matter of any one of Examples 35-42, andoptionally, wherein the first non-legacy header comprises one or moreparameters selected from the group consisting of a number of channels tobe bonded, a modulation and coding scheme, a length of at least a dataportion of the frame, a Cyclic Prefix (CP) interval, and a number ofspatial streams.

Example 44 includes the subject matter of Example 43, and optionally,comprising transmitting at least the data portion of the frame accordingto the one or more parameters.

Example 45 includes the subject matter of any one of Examples 35-44, andoptionally, wherein the header portion is to comprise the secondnon-legacy header, the second non-legacy header comprising one or moreMulti-User (MU) Multi-Input-Multi-Output (MIMO) (MU-MIMO) parameters.

Example 46 includes the subject matter of Example 45, and optionally,comprising transmitting at least a data portion of the frame to aplurality of users according to the MU-MIMO parameters.

Example 47 includes the subject matter of any one of Examples 35-46, andoptionally, wherein the legacy header comprises a Single Carrier (SC)header.

Example 48 includes the subject matter of any one of Examples 35-47, andoptionally, wherein the directional wireless communication band is aDirectional Multi-Gigabit (DMG) band.

Example 49 includes the subject matter of any one of Examples 35-48, andoptionally, wherein the first wireless station is a DirectionalMulti-Gigabit (DMG) Station (STA).

Example 50 includes a product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone computer processor, enable the at least one computer processor toimplement one or more operations at a first wireless station, theoperations comprising generating a frame comprising a header portion,the header portion comprising a legacy header, followed by a firstnon-legacy header, the header portion comprising a first indication toindicate whether or not the header portion is to comprise a secondnon-legacy header following the first non-legacy header, the headerportion comprising a second indication to indicate whether or notchannel bonding is to be used; and processing transmission of the frameto at least one second wireless station over a directional wirelesscommunication band.

Example 51 includes the subject matter of Example 50, and optionally,wherein the legacy header comprises the first and second indications.

Example 52 includes the subject matter of Example 50, and optionally,wherein the first non-legacy header comprises the first and secondindications.

Example 53 includes the subject matter of any one of Examples 50-52, andoptionally, wherein the first non-legacy header comprises a channelbitmap to indicate two or more channels to be bonded, when the secondindication is to indicate channel bonding is to be used.

Example 54 includes the subject matter of Example 53, and optionally,wherein the channel bitmap comprises a sequence of a plurality of bitscorresponding to a respective plurality of channels, a bit of thesequence of bits having a value to indicate whether or not a respectivechannel of the plurality of channels is to be bonded.

Example 55 includes the subject matter of Example 54, and optionally,wherein two non-consecutive bits of the sequence of bits have a value toindicate that two non-contiguous channels are to be bonded.

Example 56 includes the subject matter of any one of Examples 50-52, andoptionally, wherein the first non-legacy header comprises a first fieldto indicate a primary channel to be used for channel bonding, and asecond field to indicate a channel bandwidth to be used for the channelbonding.

Example 57 includes the subject matter of any one of Examples 50-56, andoptionally, wherein the operations comprise transmitting at least a dataportion of the frame over a bonded channel, when the second indicationis to indicate channel bonding is to be used.

Example 58 includes the subject matter of any one of Examples 50-57, andoptionally, wherein the first non-legacy header comprises one or moreparameters selected from the group consisting of a number of channels tobe bonded, a modulation and coding scheme, a length of at least a dataportion of the frame, a Cyclic Prefix (CP) interval, and a number ofspatial streams.

Example 59 includes the subject matter of Example 58, and optionally,wherein the operations comprise transmitting at least the data portionof the frame according to the one or more parameters.

Example 60 includes the subject matter of any one of Examples 50-59, andoptionally, wherein the header portion is to comprise the secondnon-legacy header, the second non-legacy header comprising one or moreMulti-User (MU) Multi-Input-Multi-Output (MIMO) (MU-MIMO) parameters.

Example 61 includes the subject matter of Example 60, and optionally,wherein the operations comprise transmitting at least a data portion ofthe frame to a plurality of users according to the MU-MIMO parameters.

Example 62 includes the subject matter of any one of Examples 50-61, andoptionally, wherein the legacy header comprises a Single Carrier (SC)header.

Example 63 includes the subject matter of any one of Examples 50-62, andoptionally, wherein the directional wireless communication band is aDirectional Multi-Gigabit (DMG) band.

Example 64 includes the subject matter of any one of Examples 50-63, andoptionally, wherein the first wireless station is a DirectionalMulti-Gigabit (DMG) Station (STA).

Example 65 includes a system of wireless communication comprising afirst wireless station, the first wireless station comprising one ormore directional antennas; a memory; a processor; and a radio totransmit a frame to at least one second wireless station over adirectional wireless communication band, the frame comprising a headerportion, the header portion comprising a legacy header, followed by afirst non-legacy header, the header portion comprising a firstindication to indicate whether or not the header portion is to comprisea second non-legacy header following the first non-legacy header, theheader portion comprising a second indication to indicate whether or notchannel bonding is to be used.

Example 66 includes the subject matter of Example 65, and optionally,wherein the legacy header comprises the first and second indications.

Example 67 includes the subject matter of Example 65, and optionally,wherein the first non-legacy header comprises the first and secondindications.

Example 68 includes the subject matter of any one of Examples 65-67, andoptionally, wherein the first non-legacy header comprises a channelbitmap to indicate two or more channels to be bonded, when the secondindication is to indicate channel bonding is to be used.

Example 69 includes the subject matter of Example 68, and optionally,wherein the channel bitmap comprises a sequence of a plurality of bitscorresponding to a respective plurality of channels, a bit of thesequence of bits having a value to indicate whether or not a respectivechannel of the plurality of channels is to be bonded.

Example 70 includes the subject matter of Example 69, and optionally,wherein two non-consecutive bits of the sequence of bits have a value toindicate that two non-contiguous channels are to be bonded.

Example 71 includes the subject matter of any one of Examples 65-67, andoptionally, wherein the first non-legacy header comprises a first fieldto indicate a primary channel to be used for channel bonding, and asecond field to indicate a channel bandwidth to be used for the channelbonding.

Example 72 includes the subject matter of any one of Examples 65-71, andoptionally, wherein the radio is to transmit at least a data portion ofthe frame over a bonded channel, when the second indication is toindicate channel bonding is to be used.

Example 73 includes the subject matter of any one of Examples 65-72, andoptionally, wherein the first non-legacy header comprises one or moreparameters selected from the group consisting of a number of channels tobe bonded, a modulation and coding scheme, a length of at least a dataportion of the frame, a Cyclic Prefix (CP) interval, and a number ofspatial streams.

Example 74 includes the subject matter of Example 73, and optionally,wherein the radio is to transmit at least the data portion of the frameaccording to the one or more parameters.

Example 75 includes the subject matter of any one of Examples 65-74, andoptionally, wherein the header portion is to comprise the secondnon-legacy header, the second non-legacy header comprising one or moreMulti-User (MU) Multi-Input-Multi-Output (MIMO) (MU-MIMO) parameters.

Example 76 includes the subject matter of Example 75, and optionally,wherein the radio is to transmit at least a data portion of the frame toa plurality of users according to the MU-MIMO parameters.

Example 77 includes the subject matter of any one of Examples 65-76, andoptionally, wherein the legacy header comprises a Single Carrier (SC)header.

Example 78 includes the subject matter of any one of Examples 65-77, andoptionally, wherein the directional wireless communication band is aDirectional Multi-Gigabit (DMG) band.

Example 79 includes the subject matter of any one of Examples 65-78, andoptionally, wherein the first wireless station is a DirectionalMulti-Gigabit (DMG) Station (STA).

Example 80 includes an apparatus of wireless communication, theapparatus comprising means for generating at a first wireless station aframe comprising a header portion, the header portion comprising alegacy header, followed by a first non-legacy header, the header portioncomprising a first indication to indicate whether or not the headerportion is to comprise a second non-legacy header following the firstnon-legacy header, the header portion comprising a second indication toindicate whether or not channel bonding is to be used; and means forprocessing transmission of the frame to at least one second wirelessstation over a directional wireless communication band.

Example 81 includes the subject matter of Example 80, and optionally,wherein the legacy header comprises the first and second indications.

Example 82 includes the subject matter of Example 80, and optionally,wherein the first non-legacy header comprises the first and secondindications.

Example 83 includes the subject matter of any one of Examples 80-82, andoptionally, wherein the first non-legacy header comprises a channelbitmap to indicate two or more channels to be bonded, when the secondindication is to indicate channel bonding is to be used.

Example 84 includes the subject matter of Example 83, and optionally,wherein the channel bitmap comprises a sequence of a plurality of bitscorresponding to a respective plurality of channels, a bit of thesequence of bits having a value to indicate whether or not a respectivechannel of the plurality of channels is to be bonded.

Example 85 includes the subject matter of Example 84, and optionally,wherein two non-consecutive bits of the sequence of bits have a value toindicate that two non-contiguous channels are to be bonded.

Example 86 includes the subject matter of any one of Examples 80-82, andoptionally, wherein the first non-legacy header comprises a first fieldto indicate a primary channel to be used for channel bonding, and asecond field to indicate a channel bandwidth to be used for the channelbonding.

Example 87 includes the subject matter of any one of Examples 80-86, andoptionally, comprising means for transmitting at least a data portion ofthe frame over a bonded channel, when the second indication is toindicate channel bonding is to be used.

Example 88 includes the subject matter of any one of Examples 80-87, andoptionally, wherein the first non-legacy header comprises one or moreparameters selected from the group consisting of a number of channels tobe bonded, a modulation and coding scheme, a length of at least a dataportion of the frame, a Cyclic Prefix (CP) interval, and a number ofspatial streams.

Example 89 includes the subject matter of Example 88, and optionally,comprising means for transmitting at least the data portion of the frameaccording to the one or more parameters.

Example 90 includes the subject matter of any one of Examples 80-89, andoptionally, wherein the header portion is to comprise the secondnon-legacy header, the second non-legacy header comprising one or moreMulti-User (MU) Multi-Input-Multi-Output (MIMO) (MU-MIMO) parameters.

Example 91 includes the subject matter of Example 90, and optionally,comprising means for transmitting at least a data portion of the frameto a plurality of users according to the MU-MIMO parameters.

Example 92 includes the subject matter of any one of Examples 80-91, andoptionally, wherein the legacy header comprises a Single Carrier (SC)header.

Example 93 includes the subject matter of any one of Examples 80-92, andoptionally, wherein the directional wireless communication band is aDirectional Multi-Gigabit (DMG) band.

Example 94 includes the subject matter of any one of Examples 80-93, andoptionally, wherein the first wireless station is a DirectionalMulti-Gigabit (DMG) Station (STA).

Example 95 includes a method to be performed at a first wirelessstation, the method comprising processing reception of a header portionof a frame from a second wireless station over a directional wirelesscommunication band, the header portion comprising a legacy header,followed by a first non-legacy header, the header portion comprising afirst indication to indicate whether or not the header portion is tocomprise a second non-legacy header following the first non-legacyheader, the header portion comprising a second indication to indicatewhether or not channel bonding is to be used; and processing receptionof at least a data portion of the frame based at least on the firstnon-legacy header.

Example 96 includes the subject matter of Example 95, and optionally,wherein the legacy header comprises the first and second indications.

Example 97 includes the subject matter of Example 95, and optionally,wherein the first non-legacy header comprises the first and secondindications.

Example 98 includes the subject matter of any one of Examples 95-97, andoptionally, wherein the first non-legacy header comprises a channelbitmap to indicate two or more channels to be bonded, when the secondindication is to indicate channel bonding is to be used.

Example 99 includes the subject matter of Example 98, and optionally,wherein the channel bitmap comprises a sequence of a plurality of bitscorresponding to a respective plurality of channels, a bit of thesequence of bits having a value to indicate whether or not a respectivechannel of the plurality of channels is to be bonded.

Example 100 includes the subject matter of Example 99, and optionally,wherein two non-consecutive bits of the sequence of bits have a value toindicate that two non-contiguous channels are to be bonded.

Example 101 includes the subject matter of any one of Examples 95-97,and optionally, wherein the first non-legacy header comprises a firstfield to indicate a primary channel to be used for channel bonding, anda second field to indicate a channel bandwidth to be used for thechannel bonding.

Example 102 includes the subject matter of any one of Examples 95-101,and optionally, comprising processing reception of at least the dataportion of the frame over a bonded channel, when the second indicationis to indicate channel bonding is to be used.

Example 103 includes the subject matter of any one of Examples 95-102,and optionally, wherein the first non-legacy header comprises one ormore parameters selected from the group consisting of a number ofchannels to be bonded, a modulation and coding scheme, a length of atleast a data portion of the frame, a Cyclic Prefix (CP) interval, and anumber of spatial streams.

Example 104 includes the subject matter of Example 103, and optionally,comprising processing reception of at least the data portion of theframe according to the one or more parameters.

Example 105 includes the subject matter of any one of Examples 95-104,and optionally, wherein the header portion is to comprise the secondnon-legacy header, the second non-legacy header comprising one or moreMulti-User (MU) Multi-Input-Multi-Output (MIMO) (MU-MIMO) parameters.

Example 106 includes the subject matter of Example 105, and optionally,comprising processing reception of at least the data portion of theframe according to the MU-MIMO parameters.

Example 107 includes the subject matter of any one of Examples 95-106,and optionally, wherein the legacy header comprises a Single Carrier(SC) header.

Example 108 includes the subject matter of any one of Examples 95-107,and optionally, wherein the directional wireless communication band is aDirectional Multi-Gigabit (DMG) band.

Example 109 includes the subject matter of any one of Examples 95-108,and optionally, wherein the first wireless station is a DirectionalMulti-Gigabit (DMG) Station (STA).

Example 110 includes a product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone computer processor, enable the at least one computer processor toimplement one or more operations at a first wireless station, theoperations comprising processing reception of a header portion of aframe from a second wireless station over a directional wirelesscommunication band, the header portion comprising a legacy header,followed by a first non-legacy header, the header portion comprising afirst indication to indicate whether or not the header portion is tocomprise a second non-legacy header following the first non-legacyheader, the header portion comprising a second indication to indicatewhether or not channel bonding is to be used; and processing receptionof at least a data portion of the frame based at least on the firstnon-legacy header.

Example 111 includes the subject matter of Example 110, and optionally,wherein the legacy header comprises the first and second indications.

Example 112 includes the subject matter of Example 110, and optionally,wherein the first non-legacy header comprises the first and secondindications.

Example 113 includes the subject matter of any one of Examples 110-112,and optionally, wherein the first non-legacy header comprises a channelbitmap to indicate two or more channels to be bonded, when the secondindication is to indicate channel bonding is to be used.

Example 114 includes the subject matter of Example 113, and optionally,wherein the channel bitmap comprises a sequence of a plurality of bitscorresponding to a respective plurality of channels, a bit of thesequence of bits having a value to indicate whether or not a respectivechannel of the plurality of channels is to be bonded.

Example 115 includes the subject matter of Example 114, and optionally,wherein two non-consecutive bits of the sequence of bits have a value toindicate that two non-contiguous channels are to be bonded.

Example 116 includes the subject matter of any one of Examples 110-112,and optionally, wherein the first non-legacy header comprises a firstfield to indicate a primary channel to be used for channel bonding, anda second field to indicate a channel bandwidth to be used for thechannel bonding.

Example 117 includes the subject matter of any one of Examples 110-116,and optionally, wherein the operations comprise processing reception ofat least the data portion of the frame over a bonded channel, when thesecond indication is to indicate channel bonding is to be used.

Example 118 includes the subject matter of any one of Examples 110-117,and optionally, wherein the first non-legacy header comprises one ormore parameters selected from the group consisting of a number ofchannels to be bonded, a modulation and coding scheme, a length of atleast a data portion of the frame, a Cyclic Prefix (CP) interval, and anumber of spatial streams.

Example 119 includes the subject matter of Example 118, and optionally,wherein the operations comprise processing reception of at least thedata portion of the frame according to the one or more parameters.

Example 120 includes the subject matter of any one of Examples 110-119,and optionally, wherein the header portion is to comprise the secondnon-legacy header, the second non-legacy header comprising one or moreMulti-User (MU) Multi-Input-Multi-Output (MIMO) (MU-MIMO) parameters.

Example 121 includes the subject matter of Example 120, and optionally,wherein the operations comprise processing reception of at least thedata portion of the frame according to the MU-MIMO parameters.

Example 122 includes the subject matter of any one of Examples 110-121,and optionally, wherein the legacy header comprises a Single Carrier(SC) header.

Example 123 includes the subject matter of any one of Examples 110-122,and optionally, wherein the directional wireless communication band is aDirectional Multi-Gigabit (DMG) band.

Example 124 includes the subject matter of any one of Examples 110-123,and optionally, wherein the first wireless station is a DirectionalMulti-Gigabit (DMG) Station (STA).

Example 125 includes a system of wireless communication comprising afirst wireless station, the first wireless station comprising one ormore directional antennas; a memory; a processor; and a radio to processreception of a header portion of a frame from a second wireless stationover a directional wireless communication band, the header portioncomprising a legacy header, followed by a first non-legacy header, theheader portion comprising a first indication to indicate whether or notthe header portion is to comprise a second non-legacy header followingthe first non-legacy header, the header portion comprising a secondindication to indicate whether or not channel bonding is to be used, andto process reception of at least a data portion of the frame based atleast on the first non-legacy header.

Example 126 includes the subject matter of Example 125, and optionally,wherein the legacy header comprises the first and second indications.

Example 127 includes the subject matter of Example 125, and optionally,wherein the first non-legacy header comprises the first and secondindications.

Example 128 includes the subject matter of any one of Examples 125-127,and optionally, wherein the first non-legacy header comprises a channelbitmap to indicate two or more channels to be bonded, when the secondindication is to indicate channel bonding is to be used.

Example 129 includes the subject matter of Example 128, and optionally,wherein the channel bitmap comprises a sequence of a plurality of bitscorresponding to a respective plurality of channels, a bit of thesequence of bits having a value to indicate whether or not a respectivechannel of the plurality of channels is to be bonded.

Example 130 includes the subject matter of Example 129, and optionally,wherein two non-consecutive bits of the sequence of bits have a value toindicate that two non-contiguous channels are to be bonded.

Example 131 includes the subject matter of any one of Examples 125-127,and optionally, wherein the first non-legacy header comprises a firstfield to indicate a primary channel to be used for channel bonding, anda second field to indicate a channel bandwidth to be used for thechannel bonding.

Example 132 includes the subject matter of any one of Examples 125-131,and optionally, wherein the radio is to process reception of at leastthe data portion of the frame over a bonded channel, when the secondindication is to indicate channel bonding is to be used.

Example 133 includes the subject matter of any one of Examples 125-132,and optionally, wherein the first non-legacy header comprises one ormore parameters selected from the group consisting of a number ofchannels to be bonded, a modulation and coding scheme, a length of atleast a data portion of the frame, a Cyclic Prefix (CP) interval, and anumber of spatial streams.

Example 134 includes the subject matter of Example 133, and optionally,wherein the radio is to process reception of at least the data portionof the frame according to the one or more parameters.

Example 135 includes the subject matter of any one of Examples 125-134,and optionally, wherein the header portion is to comprise the secondnon-legacy header, the second non-legacy header comprising one or moreMulti-User (MU) Multi-Input-Multi-Output (MIMO) (MU-MIMO) parameters.

Example 136 includes the subject matter of Example 135, and optionally,wherein the radio is to process reception of at least the data portionof the frame according to the MU-MIMO parameters.

Example 137 includes the subject matter of any one of Examples 125-136,and optionally, wherein the legacy header comprises a Single Carrier(SC) header.

Example 138 includes the subject matter of any one of Examples 125-137,and optionally, wherein the directional wireless communication band is aDirectional Multi-Gigabit (DMG) band.

Example 139 includes the subject matter of any one of Examples 125-138,and optionally, wherein the first wireless station is a DirectionalMulti-Gigabit (DMG) Station (STA).

Example 140 includes an apparatus of wireless communication, theapparatus comprising means for processing at a first wireless stationreception of a header portion of a frame from a second wireless stationover a directional wireless communication band, the header portioncomprising a legacy header, followed by a first non-legacy header, theheader portion comprising a first indication to indicate whether or notthe header portion is to comprise a second non-legacy header followingthe first non-legacy header, the header portion comprising a secondindication to indicate whether or not channel bonding is to be used; andmeans for processing reception of at least a data portion of the framebased at least on the first non-legacy header.

Example 141 includes the subject matter of Example 140, and optionally,wherein the legacy header comprises the first and second indications.

Example 142 includes the subject matter of Example 140, and optionally,wherein the first non-legacy header comprises the first and secondindications.

Example 143 includes the subject matter of any one of Examples 140-142,and optionally, wherein the first non-legacy header comprises a channelbitmap to indicate two or more channels to be bonded, when the secondindication is to indicate channel bonding is to be used.

Example 144 includes the subject matter of Example 143, and optionally,wherein the channel bitmap comprises a sequence of a plurality of bitscorresponding to a respective plurality of channels, a bit of thesequence of bits having a value to indicate whether or not a respectivechannel of the plurality of channels is to be bonded.

Example 145 includes the subject matter of Example 144, and optionally,wherein two non-consecutive bits of the sequence of bits have a value toindicate that two non-contiguous channels are to be bonded.

Example 146 includes the subject matter of any one of Examples 140-142,and optionally, wherein the first non-legacy header comprises a firstfield to indicate a primary channel to be used for channel bonding, anda second field to indicate a channel bandwidth to be used for thechannel bonding.

Example 147 includes the subject matter of any one of Examples 140-146,and optionally, comprising means for processing reception of at leastthe data portion of the frame over a bonded channel, when the secondindication is to indicate channel bonding is to be used.

Example 148 includes the subject matter of any one of Examples 140-147,and optionally, wherein the first non-legacy header comprises one ormore parameters selected from the group consisting of a number ofchannels to be bonded, a modulation and coding scheme, a length of atleast a data portion of the frame, a Cyclic Prefix (CP) interval, and anumber of spatial streams.

Example 149 includes the subject matter of Example 148, and optionally,comprising means for processing reception of at least the data portionof the frame according to the one or more parameters.

Example 150 includes the subject matter of any one of Examples 140-149,and optionally, wherein the header portion is to comprise the secondnon-legacy header, the second non-legacy header comprising one or moreMulti-User (MU) Multi-Input-Multi-Output (MIMO) (MU-MIMO) parameters.

Example 151 includes the subject matter of Example 150, and optionally,comprising means for processing reception of at least the data portionof the frame according to the MU-MIMO parameters.

Example 152 includes the subject matter of any one of Examples 140-151,and optionally, wherein the legacy header comprises a Single Carrier(SC) header.

Example 153 includes the subject matter of any one of Examples 140-152,and optionally, wherein the directional wireless communication band is aDirectional Multi-Gigabit (DMG) band.

Example 154 includes the subject matter of any one of Examples 140-153,and optionally, wherein the first wireless station is a DirectionalMulti-Gigabit (DMG) Station (STA).

Functions, operations, components and/or features described herein withreference to one or more embodiments, may be combined with, or may beutilized in combination with, one or more other functions, operations,components and/or features described herein with reference to one ormore other embodiments, or vice versa.

While certain features have been illustrated and described herein, manymodifications, substitutions, changes, and equivalents may occur tothose skilled in the art. It is, therefore, to be understood that theappended claims are intended to cover all such modifications and changesas fall within the true spirit of the disclosure.

What is claimed is:
 1. An apparatus comprising logic and circuitryconfigured to cause a wireless communication station to: generate aPhysical Layer Protocol Data Unit (PPDU) comprising a first header fieldand a second header (Header A) field after the first header field, theHeader A field comprising a first field having a value according towhether or not the PPDU is to include a third header (Header B) fieldafter the Header A field, the Header A field comprising at least onesecond field to indicate a channel bandwidth comprising one channel ortwo or more channels; and transmit said PPDU over the channel bandwidthin a frequency band above 45 Gigahertz (GHz).
 2. The apparatus of claim1, wherein the first field of the Header A field comprises a first valuewhen the PPDU is a Single-User (SU) PPDU without the Header B field, andwherein the first field of the Header A field comprises a second valuewhen the PPDU is a Multi-User (MU) PPDU comprising the Header B field.3. The apparatus of claim 2, wherein the Header B field comprisesSpatial Stream (SS) information corresponding to the MU PPDU.
 4. Theapparatus of claim 1, wherein the first field of the Header A field hasa value of “1” when the PPDU is to include the Header B field.
 5. Theapparatus of claim 1, wherein the Header A field comprises a channelbitmap comprising a plurality of bits corresponding to a respectiveplurality of channels, a bit of the plurality of bits having a firstvalue when a channel corresponding to the bit is to be used for thechannel bandwidth, the bit having a second value when the channelcorresponding to the bit is not to be used for the channel bandwidth. 6.The apparatus of claim 5, wherein the channel bitmap comprises 8 bits.7. The apparatus of claim 1, wherein the Header A field comprises aprimary channel field based on a channel number of a primary channel ofa Basic Service Set (BSS).
 8. The apparatus of claim 1, wherein the PPDUcomprises a data field, and a Training (TRN) field after the data field.9. The apparatus of claim 1, wherein the first header field comprises aSingle Carrier (SC) field.
 10. The apparatus of claim 1, wherein thefirst header field comprises at least one of a scrambler initializationfield, a length field, or a Last Received Signal Strength Indication(RSSI) field.
 11. The apparatus of claim 1, wherein the channelbandwidth comprises a plurality of contiguous channels.
 12. Theapparatus of claim 1, wherein the channel bandwidth comprises aplurality of non-contiguous channels.
 13. The apparatus of claim 1,wherein the channel bandwidth comprises channel bonding of the two ormore channels.
 14. The apparatus of claim 1, wherein the channelbandwidth comprises a channel bandwidth of 4.32 GHz or 6.48 GHz.
 15. Theapparatus of claim 1, wherein the PPDU comprises an Extended DirectionalMulti-Gigabit (EDMG) PPDU, the Header A field comprises an EDMG Header Afield, and the Header B field comprises an EDMG Header B field.
 16. Theapparatus of claim 1 comprising a Medium Access Control (MAC), and aPhysical Layer (PHY).
 17. The apparatus of claim 1 comprising a radio.18. The apparatus of claim 1 comprising one or more antennas.
 19. Aproduct comprising one or more tangible computer-readable non-transitorystorage media comprising computer-executable instructions operable to,when executed by at least one processor, enable the at least oneprocessor to cause a wireless communication station to: generate aPhysical Layer Protocol Data Unit (PPDU) comprising a first header fieldand a second header (Header A) field after the first header field, theHeader A field comprising a first field having a value according towhether or not the PPDU is to include a third header (Header B) fieldafter the Header A field, the Header A field comprising at least onesecond field to indicate a channel bandwidth comprising one channel ortwo or more channels; and transmit said PPDU over the channel bandwidthin a frequency band above 45 Gigahertz (GHz).
 20. The product of claim19, wherein the first field of the Header A field comprises a firstvalue when the PPDU is a Single-User (SU) PPDU without the Header Bfield, and wherein the first field of the Header A field comprises asecond value when the PPDU is a Multi-User (MU) PPDU comprising theHeader B field.
 21. The product of claim 20, wherein the Header B fieldcomprises Spatial Stream (SS) information corresponding to the MU PPDU.22. The product of claim 19, wherein the Header A field comprises achannel bitmap comprising a plurality of bits corresponding to arespective plurality of channels, a bit of the plurality of bits havinga first value when a channel corresponding to the bit is to be used forthe channel bandwidth, the bit having a second value when the channelcorresponding to the bit is not to be used for the channel bandwidth.23. The product of claim 19, wherein the Header A field comprises aprimary channel field based on a channel number of a primary channel ofa Basic Service Set (BSS).
 24. The product of claim 19, wherein the PPDUcomprises a data field, and a Training (TRN) field after the data field.25. The product of claim 19, wherein the first header field comprises atleast one of a scrambler initialization field, a length field, or a LastReceived Signal Strength Indication (RSSI) field.
 26. The product ofclaim 19, wherein the channel bandwidth comprises channel bonding of thetwo or more channels.
 27. The product of claim 19, wherein the channelbandwidth comprises a channel bandwidth of 4.32 GHz or 6.48 GHz.
 28. Theproduct of claim 19, wherein the PPDU comprises an Extended DirectionalMulti-Gigabit (EDMG) PPDU, the Header A field comprises an EDMG Header Afield, and the Header B field comprises an EDMG Header B field.
 29. Anapparatus comprising logic and circuitry configured to cause a wirelesscommunication station to: receive a first header field and a secondheader (Header A) field of a Physical Layer Protocol Data Unit (PPDU),the Header A field is after the first header field, the Header A fieldcomprising a first field having a value according to whether or not thePPDU is to include a third header (Header B) field after the Header Afield, the Header A field comprising at least one second field toindicate a channel bandwidth comprising one channel or two or morechannels; and based at least on the Header A field, process at least adata field of said PPDU over the channel bandwidth in a frequency bandabove 45 Gigahertz (GHz).
 30. The apparatus of claim 29, wherein thefirst field of the Header A field comprises a first value when the PPDUis a Single-User (SU) PPDU without the Header B field, and wherein thefirst field of the Header A field comprises a second value when the PPDUis a Multi-User (MU) PPDU comprising the Header B field.
 31. Theapparatus of claim 30, wherein the Header B field comprises SpatialStream (SS) information corresponding to the MU PPDU.
 32. The apparatusof claim 29, wherein the first field of the Header A field has a valueof “1” when the PPDU is to include the Header B field.
 33. The apparatusof claim 29, wherein the Header A field comprises a channel bitmapcomprising a plurality of bits corresponding to a respective pluralityof channels, a bit of the plurality of bits having a first value when achannel corresponding to the bit is to be used for the channelbandwidth, the bit having a second value when the channel correspondingto the bit is not to be used for the channel bandwidth.
 34. Theapparatus of claim 33, wherein the channel bitmap comprises 8 bits. 35.The apparatus of claim 29, wherein the Header A field comprises aprimary channel field based on a channel number of a primary channel ofa Basic Service Set (BSS).
 36. The apparatus of claim 29, wherein thePPDU comprises a Training (TRN) field after the data field.
 37. Theapparatus of claim 29, wherein the first header field comprises a SingleCarrier (SC) field.
 38. The apparatus of claim 29, wherein the firstheader field comprises at least one of a scrambler initialization field,a length field, or a Last Received Signal Strength Indication (RSSI)field.
 39. The apparatus of claim 29, wherein the channel bandwidthcomprises a plurality of contiguous channels.
 40. The apparatus of claim29, wherein the channel bandwidth comprises a plurality ofnon-contiguous channels.
 41. The apparatus of claim 29, wherein thechannel bandwidth comprises channel bonding of the two or more channels.42. The apparatus of claim 29, wherein the channel bandwidth comprises achannel bandwidth of 4.32 GHz or 6.48 GHz.
 43. The apparatus of claim29, wherein the PPDU comprises an Extended Directional Multi-Gigabit(EDMG) PPDU, the Header A field comprises an EDMG Header A field, andthe Header B field comprises an EDMG Header B field.
 44. The apparatusof claim 29 comprising a Medium Access Control (MAC), and a PhysicalLayer (PHY).
 45. The apparatus of claim 29 comprising a radio.
 46. Theapparatus of claim 29 comprising one or more antennas.
 47. A productcomprising one or more tangible computer-readable non-transitory storagemedia comprising computer-executable instructions operable to, whenexecuted by at least one processor, enable the at least one processor tocause a wireless communication station to: receive a first header fieldand a second header (Header A) field of a Physical Layer Protocol DataUnit (PPDU), the Header A field is after the first header field, theHeader A field comprising a first field having a value according towhether or not the PPDU is to include a third header (Header B) fieldafter the Header A field, the Header A field comprising at least onesecond field to indicate a channel bandwidth comprising one channel ortwo or more channels; and based at least on the Header A field, processat least a data field of said PPDU over the channel bandwidth in afrequency band above 45 Gigahertz (GHz).
 48. The product of claim 47,wherein the first field of the Header A field comprises a first valuewhen the PPDU is a Single-User (SU) PPDU without the Header B field, andwherein the first field of the Header A field comprises a second valuewhen the PPDU is a Multi-User (MU) PPDU comprising the Header B field.49. The product of claim 48, wherein the Header B field comprisesSpatial Stream (SS) information corresponding to the MU PPDU.
 50. Theproduct of claim 47, wherein the Header A field comprises a channelbitmap comprising a plurality of bits corresponding to a respectiveplurality of channels, a bit of the plurality of bits having a firstvalue when a channel corresponding to the bit is to be used for thechannel bandwidth, the bit having a second value when the channelcorresponding to the bit is not to be used for the channel bandwidth.51. The product of claim 47, wherein the Header A field comprises aprimary channel field based on a channel number of a primary channel ofa Basic Service Set (BSS).
 52. The product of claim 47, wherein the PPDUcomprises a Training (TRN) field after the data field.
 53. The productof claim 47, wherein the first header field comprises at least one of ascrambler initialization field, a length field, or a Last ReceivedSignal Strength Indication (RSSI) field.
 54. The product of claim 47,wherein the channel bandwidth comprises channel bonding of the two ormore channels.
 55. The product of claim 47, wherein the channelbandwidth comprises a channel bandwidth of 4.32 GHz or 6.48 GHz.